ci(build): Add snapshot release workflow #3212
+149
−1
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,114 @@ | ||
| name: Snapshot Release | ||
|
|
||
| on: | ||
|
Contributor
Author
There was a problem hiding this comment. manual trigger to test. we can change this to build on every push to master once we know it is working.
Member
There was a problem hiding this comment. l: I would be fine with just having it set to every push to master with this PR. We can revert if needed |
||
| workflow_dispatch: | ||
|
|
||
| permissions: | ||
| contents: write | ||
|
|
||
| jobs: | ||
| prepare: | ||
| name: Prepare Snapshot | ||
| runs-on: ubuntu-24.04 | ||
| outputs: | ||
| version: ${{ steps.version.outputs.version }} | ||
| ref: ${{ steps.push.outputs.ref }} | ||
| steps: | ||
| - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # 6.0.2 | ||
|
|
||
| # Computes a semver-compliant snapshot version based on the current | ||
| # version in Cargo.toml. The minor version is bumped so that the | ||
| # snapshot sorts higher than the current release but lower than the | ||
| # next real release. For example, if Cargo.toml has 3.3.1, the | ||
| # snapshot version will be 3.4.0-snapshot.20260312.abc1234. | ||
|
runningcode marked this conversation as resolved.
Outdated
|
||
| - name: Compute snapshot version | ||
| id: version | ||
| run: | | ||
| CURRENT=$(grep '^version = ' Cargo.toml | head -1 | sed 's/version = "\(.*\)"/\1/') | ||
|
runningcode marked this conversation as resolved.
Outdated
|
||
| MAJOR=$(echo "$CURRENT" | cut -d. -f1) | ||
| MINOR=$(echo "$CURRENT" | cut -d. -f2) | ||
| NEXT_MINOR=$((MINOR + 1)) | ||
| DATE=$(date -u +%Y%m%d) | ||
| SHORT_SHA=$(git rev-parse --short HEAD) | ||
| VERSION="${MAJOR}.${NEXT_MINOR}.0-snapshot.${DATE}.${SHORT_SHA}" | ||
| echo "version=$VERSION" >> "$GITHUB_OUTPUT" | ||
| echo "current=$CURRENT" >> "$GITHUB_OUTPUT" | ||
| echo "Snapshot version: $VERSION" | ||
|
|
||
| - uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # 6.2.0 | ||
| with: | ||
| node-version: '20.10.0' | ||
|
|
||
| - name: Bump versions | ||
|
Contributor
Author
There was a problem hiding this comment. so another way to do this would be to modify the versions in place in the action/workflow using sed and regexes. this would remove the need to commit and create the snapshot branch somewhere but then we have two different mechanisms to patch the versions which could lead to drift. without modifying in place, there's no way to share the patched repo between workflows. |
||
| run: scripts/bump-version.sh "${{ steps.version.outputs.current }}" "${{ steps.version.outputs.version }}" | ||
|
|
||
| - name: Push snapshot branch | ||
| id: push | ||
| run: | | ||
| BRANCH="snapshot/${{ steps.version.outputs.version }}" | ||
| git config user.name "github-actions[bot]" | ||
| git config user.email "github-actions[bot]@users.noreply.github.com" | ||
| git checkout -b "$BRANCH" | ||
| git add -A | ||
| git commit -m "snapshot: ${{ steps.version.outputs.version }}" | ||
| git push origin "$BRANCH" | ||
| echo "ref=$BRANCH" >> "$GITHUB_OUTPUT" | ||
|
|
||
| build: | ||
| name: Build | ||
| needs: prepare | ||
| uses: ./.github/workflows/build.yml | ||
| with: | ||
| skip-signing: true | ||
| is-snapshot: true | ||
| checkout-ref: ${{ needs.prepare.outputs.ref }} | ||
| secrets: inherit | ||
|
|
||
| publish-npm: | ||
| name: Publish to npm | ||
| needs: [prepare, build] | ||
| runs-on: ubuntu-24.04 | ||
| steps: | ||
| - uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # 6.2.0 | ||
| with: | ||
| node-version: '20.10.0' | ||
| registry-url: 'https://registry.npmjs.org' | ||
|
|
||
| - name: Download npm binary distributions | ||
| uses: actions/download-artifact@70fc10c6e5e1ce46ad2ea6f2b72d43f7d47b13c3 # 8.0.0 | ||
| with: | ||
| name: artifact-npm-binary-distributions | ||
| path: npm-distributions | ||
|
|
||
| - name: Download node package | ||
| uses: actions/download-artifact@70fc10c6e5e1ce46ad2ea6f2b72d43f7d47b13c3 # 8.0.0 | ||
| with: | ||
| name: artifact-pkg-node | ||
| path: node-package | ||
|
|
||
| - name: Publish platform packages | ||
| env: | ||
| NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} | ||
| run: | | ||
| for pkg in npm-distributions/*.tgz; do | ||
| echo "Publishing $pkg" | ||
| npm publish "$pkg" --tag snapshot | ||
| done | ||
|
cursor[bot] marked this conversation as resolved.
|
||
|
|
||
| - name: Publish main package | ||
|
sentry[bot] marked this conversation as resolved.
|
||
| env: | ||
| NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} | ||
| run: | | ||
| npm publish node-package/*.tgz --tag snapshot | ||
|
|
||
| cleanup: | ||
| name: Cleanup | ||
| needs: [prepare, publish-npm] | ||
| if: always() | ||
| runs-on: ubuntu-24.04 | ||
| steps: | ||
| - name: Delete snapshot branch | ||
|
szokeasaurusrex marked this conversation as resolved.
|
||
| env: | ||
| GH_TOKEN: ${{ github.token }} | ||
| run: | | ||
| gh api -X DELETE "repos/${{ github.repository }}/git/refs/heads/${{ needs.prepare.outputs.ref }}" || true | ||
|
cursor[bot] marked this conversation as resolved.
Outdated
|
||
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we need this checkout-ref to share the version patched repo between workflows. see comment here for more details: https://github.com/getsentry/sentry-cli/pull/3212/changes#r2924915514