Repository navigation
Release the CLI and the SDKs from the publish run, at its version - #169
Merged
Merged
Conversation
…stead of from tags nuget-publish.yml calls cli-release.yml and sdk-release.yml with the version it published the packages with, so nothing is tagged by hand. A prerelease (a run by hand on another branch) releases the CLI as a pre-release and doesn't publish the SDKs. The install script installs the latest release, a pre-release only when named.
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
📒 Files selected for processing (6)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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
1 participant
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.
No more tagging by hand.
nuget-publish.ymlnow calls two workflows with the version it just published the NuGet packages with (determine-semver: the next patch onmain):cli-release.ymlreleases thesw-serverlessCLI ascli-v<version>, marked latest, with self-contained binaries for 7 platforms andSHA256SUMS.sdk-release.ymlpublishessw-serverlessto PyPI and@simplyworks/sw-serverlessto npm at that version. It writes the version intopyproject.toml,package.jsonand the SDKs'SDK_VERSIONconstants, then tests, then publishes. It usesPYPI_API_TOKENandNPM_TOKENthroughsecrets: inherit, and a version already on a registry is skipped.A manual run on another branch gives a prerelease version: the CLI goes out as a pre-release
cli-v<x.y.z>-stg.<run>and the SDKs are skipped.scripts/install-cli.shinstalls the newest release and never a pre-release unlessSW_SERVERLESS_VERSIONnames it.Merging this runs the whole chain: NuGet, then the CLI release, then PyPI and npm.