Build pre-release VSIX in CI #1450
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
matthewbastien
added
the
full-test-run
matthewbastien
requested review from
adam-fowler,
0xTim and
award999
as code owners
award999
reviewed
Mar 20, 2025
matthewbastien
force-pushed
the
pre-release-script
branch
from
3ceed63 to
d73f726
Compare
rbenegal
reviewed
Mar 20, 2025
rbenegal
reviewed
Mar 20, 2025
award999
approved these changes
Mar 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update the
preview-packagescript to generate a pre-release package with one minor version greater than the current version from thepackage.jsonand a patch number set to today's date formatted asYYYYMMddhhmm. The nightly CI will now generate both a release and pre-release extension VSIX. This enables us to create a pre-release version of the Swift extension.Going forward, we'll have to abide by the following rules in order for this to work:
package.jsonshould always be the current release version of the extension as published on the VS Code marketplace.I've added a check in CI to enforce even numbered minor versions in the
package.json.