Afonso Jorge Ramos

Could be as well, yes, however, I'm not sure which one I prefer... In theory, we should always focus on the latest of everything as we've discussed again and again....

Thinking in my head, that seems very complicated to do (fixing certain commit hashes, etc.), but it can be something to support in the future indeed.

@CharlieS1103 that sounds good actually, but let's move that discussion to later. Once we close this issue we can touch again on this.

> > Ideas include: use a specific version/commit in the url. Save the commit ID in localstorage, and check the latest commit on load (in extension.js), and update that in...

@CharlieS1103 I understand your point, but you don't need to evaluate anyone's code, you just need to check for malicious code, which is a far easier and simpler task in...

@CharlieS1103 @theRealPadster I've been thinking over this for a while and I think it is time that we move towards a centralised manifest point of view. That is, having a...

Do you really think that people would not submit a PR out of laziness after dedicating a lot of work to creating said extension in the first place? I firmly...

I'm going to assign myself and try to tackle it then (or at least try to give it an initial push)!

@smac89 👀 > "We recommend creating releases using semantically versioned tags – for example, v1.1.3 – and keeping major (v1) and minor (v1.1) tags current to the latest appropriate commit."...

I'll test it out locally, but what VSCode shows is this: