1.17 Pre-release

[bmewburn]

1.17 is available as a pre-release. If you come across any bugs please create a new issue with a reproducible code example. Please also check the output tab and paste any relevant messages/errors you see. Thankyou!

To switch to the pre-release, search for intelephense in the VSCode extension tab and click Switch to Pre-release Version.

npm server packages are beta tagged eg 1.17.0-beta.

[willrowe]

I know I have brought this up before, but I just wanted to reiterate that the way the versioning is done between here and npm can be confusing and inconsistent.

In npm semantic versioning used to be used consistently like so:

• 1.10.0-beta.1
• 1.10.0-beta.2
• 1.10.0-beta.3
• 1.10.0-beta.4
• 1.10.0

Recently it has started skipping from a pre-release version to the next stable version without releasing a stable version of the pre-release like so:

• v1.15.0-beta.1
• v1.15.1
  instead of:
• v1.15.0-beta.1
• v1.15.0

In GitHub the releases are sometimes marked as Pre-release and sometimes not (1.13.0 is and 1.15.0 is not). The release tags do not match the corresponding tags in npm, so pre-releases are not tagged as such. 1.15.0-beta.1 in npm is just 1.15.0 in GitHub.

The skipping of versions from pre-release to stable isn't that big of a deal, but if the versions in GitHub could match the corresponding versions in npm and be marked as pre-release when appropriate, it would be very helpful for maintaining a downstream project.

Thanks for all your hard work on this project, it's an important part of my daily workflow!

[bmewburn]

In GitHub the releases are sometimes marked as Pre-release and sometimes not (1.13.0 is and 1.15.0 is not).

1.15 was an anomaly as it was meant to be pre-release but accidently made a full release.

The skipping of versions from pre-release to stable isn't that big of a deal, but if the versions in GitHub could match the corresponding versions in npm and be marked as pre-release when appropriate

VSCode doesn't support beta tags, which is why there's a difference. VSCode docs recommend using odd minor versions as pre-releases.

If there's been some substantial code changes we may release a pre-release like this one (1.17) and use an odd minor version with a beta tag on the corresponding npm server package. When the full release is ready then it gets released as the next even minor version (1.18) and the odd npm beta tagged version never gets a full release.

It's not ideal but I don't know of a better way given vscode constraints.

[willrowe]

@bmewburn understood, thanks for the explanation. Again, very appreciative for all the time you put into this!