Spruce release workflows #131
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
jhamon
commented
Oct 3, 2023
| run: | | ||
| currentVersion=$(jq -r '.version' package.json) | ||
| timestamp=$(date +%Y%m%d%H%M%S) | ||
| devVersion="$currentVersion-spruceDev.$timestamp" |
There was a problem hiding this comment.
devVersion string changed to reflect spruceDev
jhamon
commented
Oct 3, 2023
| - name: Checkout | ||
| uses: actions/checkout@v4 | ||
| with: | ||
| ref: spruce |
There was a problem hiding this comment.
Build the spruce branch
jhamon
commented
Oct 3, 2023
| jq --null-input --arg version "$devVersion" '{"name": "@pinecone-database/pinecone", "version": $version}' > src/version.json | ||
|
|
||
| - name: 'Publish to npm' | ||
| run: npm publish --tag spruceDev |
There was a problem hiding this comment.
Publish with spruceDev tag.
jhamon
commented
Oct 3, 2023
| jq --null-input --arg version "$devVersion" '{"name": "@pinecone-database/pinecone", "version": $version}' > src/version.json | ||
|
|
||
| - name: 'Publish to npm' | ||
| run: npm publish --tag spruce |
There was a problem hiding this comment.
Release with spruce tag
jhamon
commented
Oct 3, 2023
| run: | | ||
| currentVersion=$(jq -r '.version' package.json) | ||
| timestamp=$(date +%Y%m%d%H%M%S) | ||
| devVersion="$currentVersion-spruce.$timestamp" |
There was a problem hiding this comment.
devVersion string updated to have spruce identifier
jhamon
commented
Oct 3, 2023
| - name: Checkout | ||
| uses: actions/checkout@v4 | ||
| with: | ||
| ref: spruce |
jhamon
commented
Oct 3, 2023
| name: 'Release: @spruce build' | ||
|
|
||
| on: | ||
| workflow_dispatch: {} |
There was a problem hiding this comment.
Only run when manually triggered. Since there are no automatic builds of this job, we can remove the steps that checked whether there are any recent changes (designed to prevent cluttering up npm with a lot of identical builds).
jhamon
commented
Oct 3, 2023
| on: | ||
| workflow_dispatch: {} | ||
| schedule: | ||
| - cron: '0 0 * * *' |
There was a problem hiding this comment.
Run every night, or when manually triggered
austin-denoble
approved these changes
Oct 3, 2023
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.
Problem
We need a way to ship builds of the
sprucebranch.Solution
Copy & modify the existing release process for shipping dev builds of main using the
@nexttag.In these new workflows, we will use the npm tag
@spruceand@spruceDev.@sprucereleases are for use in 3rd party testing@spruceDevreleases are for use in internal testingType of Change