Skip to content

feat: add firepitOnly and dockerOnly release modes, support version overrides, and increase timeout - #10878

Open
joehan wants to merge 3 commits into
mainfrom
feat-release-script-improvements
Open

feat: add firepitOnly and dockerOnly release modes, support version overrides, and increase timeout#10878
joehan wants to merge 3 commits into
mainfrom
feat-release-script-improvements

Conversation

@joehan

@joehan joehan commented Jul 31, 2026

Copy link
Copy Markdown
Member

Description

Adds support for running selective release stages and specific versions when publishing artifacts:

  • Introduces firepitOnly and dockerOnly modes to build and publish only those specific artifacts.
  • Introduces a --version-number flag for artifactsOnly, firepitOnly, and dockerOnly runs to override the latest NPM version lookup.
  • Increases the Cloud Build execution timeout to 60 minutes (3600s) to prevent jobs from timing out under load.

Scenarios Tested

  • Submitting dockerOnly one-off Cloud Build jobs.
  • Local syntax and parameter parsing validation.

…verrides, and increase timeout

### Description
Adds support for running selective release stages and specific versions when publishing artifacts:
- Introduces `firepitOnly` and `dockerOnly` modes to build and publish only those specific artifacts.
- Introduces a `--version-number` flag for `artifactsOnly`, `firepitOnly`, and `dockerOnly` runs to override the latest NPM version lookup.
- Increases the Cloud Build execution timeout to 60 minutes (`3600s`) to prevent jobs from timing out under load.

### Scenarios Tested
- Submitting dockerOnly one-off Cloud Build jobs.
- Local syntax and parameter parsing validation.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces new publishing modes (artifactsOnly, firepitOnly, and dockerOnly) and an optional --version-number argument to the release pipeline scripts. The review feedback highlights two issues: first, in dockerOnly or artifactsOnly modes, the docker image's package-lock.json is not updated to the target version, resulting in an incorrect version of firebase-tools being packaged; second, the run.sh script can crash if --version-number is provided without a corresponding value.

Comment thread scripts/publish/cloudbuild.yaml
Comment thread scripts/publish/run.sh
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants