Support preview releases in publish script #9170
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
![google-labs-jules[bot]](https://avatars.githubusercontent.com/in/842251?s=60&v=4){kind=small}
The publish script has been updated to support a new 'preview' version. When releasing a preview version, the following changes occur: - A branch name must be provided, and the release will be built from that branch. - The npm package is published with a '--tag=preview' flag. - The following steps are skipped: - Pushing changes to the master branch. - Creating a GitHub release. - Generating firepit artifacts. - Generating a Docker image.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll acknowledge your comments with a 👀 emoji and then get to work. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! I will automatically address your feedback. For any comments you don't want me to act on, just include (aside). For security, I will only act on instructions from the user who triggered this task for this pull request. |
Updates the preview release functionality to include the sanitized branch name in the npm prerelease version string and the npm distribution tag. This allows for multiple preview versions from different branches to coexist without conflicting.
mbleigh
approved these changes
Sep 23, 2025
github-project-automation
bot
moved this to Approved [PR]
in [Cloud] Extensions + Functions
github-project-automation
bot
moved this from Approved [PR]
to Done
in [Cloud] Extensions + Functions
annajowang
pushed a commit
that referenced
this pull request
Sep 26, 2025
* feat: support preview releases in publish script The publish script has been updated to support a new 'preview' version. When releasing a preview version, the following changes occur: - A branch name must be provided, and the release will be built from that branch. - The npm package is published with a '--tag=preview' flag. - The following steps are skipped: - Pushing changes to the master branch. - Creating a GitHub release. - Generating firepit artifacts. - Generating a Docker image. * feat: include branch name in preview release version and tag Updates the preview release functionality to include the sanitized branch name in the npm prerelease version string and the npm distribution tag. This allows for multiple preview versions from different branches to coexist without conflicting. --------- Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
jrothfeder
pushed a commit
that referenced
this pull request
Oct 2, 2025
* feat: support preview releases in publish script The publish script has been updated to support a new 'preview' version. When releasing a preview version, the following changes occur: - A branch name must be provided, and the release will be built from that branch. - The npm package is published with a '--tag=preview' flag. - The following steps are skipped: - Pushing changes to the master branch. - Creating a GitHub release. - Generating firepit artifacts. - Generating a Docker image. * feat: include branch name in preview release version and tag Updates the preview release functionality to include the sanitized branch name in the npm prerelease version string and the npm distribution tag. This allows for multiple preview versions from different branches to coexist without conflicting. --------- Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
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.
This change updates the release script to support preview versions. It accepts a new option for the version argument 'preview', and an additional argument 'branch'. Instead of building off of master, it builds off of that provided branch. When releasing a preview version, it skips pushing changes back to the master branch, uploading a github release, generating firepit artifacts, and generating a docker image.
PR created automatically by Jules for task 17516625543263453881