chore(azure): record published package version 1.0.2 - #952
Merged
Merged
Conversation
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The Azure Marketplace offer went live on package version 1.0.2 this morning, so the file that tracks it is now one behind.
deploy/azure/package-version.txtis described indeploy/azure/README.mdas the single source of truth and the runbook says to bump it for every publish. The workflow's own summary says the same thing, and spells out why: leave it at the old number and the next build reuses a version Partner Center has already seen, which it rejects.What was published, for the record:
single-vmOnly the version file changes.
bun tests/run-tests.ts tests/unit/build-azure-package.test.tspasses with 40 tests, andbun run formatreports no fixes.