Skip to content

fix: updated release flow to match the current flows#10562

Merged
jasonsaayman merged 2 commits intov1.xfrom
fix/update-release-branch-flow
Mar 25, 2026
Merged

fix: updated release flow to match the current flows#10562
jasonsaayman merged 2 commits intov1.xfrom
fix/update-release-branch-flow

Conversation

@jasonsaayman
Copy link
Copy Markdown
Member

@jasonsaayman jasonsaayman commented Mar 25, 2026

Summary by cubic

Updates the release-branch workflow to build, upload, and test the packed npm tarball, aligning with the current publish flow. Adds CJS/ESM module tests across Node versions and removes the dependency review step.

Description

  • Summary of changes

    • Pack tarball with npm pack and upload axios-*.tgz as axios-tarball (fail if missing).
    • Update smoke tests to install from the packed tarball.
    • Add CJS module tests on Node 12/14/16/18.
    • Add ESM module tests on Node 20/22/24.
    • Migrate to actions/checkout@v6, actions/setup-node@v6, actions/upload-artifact@v7, actions/download-artifact@v8.
    • Remove dependency review step.
  • Reasoning

    • Test the exact artifact we publish to npm.
    • Validate CJS/ESM behavior across supported Node versions.
    • Simplify the flow by dropping an unnecessary step.
  • Additional context

    • Artifact renamed from axios (dist) to axios-tarball (npm pack).
    • Tarball installed via npm install --no-save ../../../artifacts/axios-*.tgz.
    • Review: should bump-version-and-create-pr also depend on the new module test jobs to fully gate releases?

Testing

  • No unit tests changed.
  • CI updates:
    • Smoke tests now install axios from the packed tarball.
    • New module test jobs for CJS and ESM across Node versions.
  • No additional tests needed beyond these CI checks; they cover the publishable artifact end-to-end.

Written for commit 183fedd. Summary will update on new commits.

@jasonsaayman jasonsaayman self-assigned this Mar 25, 2026
@jasonsaayman jasonsaayman added priority::high A high priority issue commit::fix The PR is related to a bugfix labels Mar 25, 2026
Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

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

1 issue found across 1 file

Confidence score: 4/5

  • This PR looks safe to merge overall, with one moderate workflow configuration risk rather than an application/runtime regression.
  • In .github/workflows/release-branch.yml, actions/dependency-review-action is used under workflow_dispatch without base-ref/head-ref; on non-PR events this can cause the dependency review step to run with incomplete context or fail to compare changes as intended.
  • Given the issue is medium severity (5/10) with reasonably strong confidence (7/10) and scoped to CI behavior, the merge risk appears limited but worth addressing soon.
  • Pay close attention to .github/workflows/release-branch.yml - dependency-review inputs for manual dispatch are likely incomplete without explicit refs.
Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name=".github/workflows/release-branch.yml">

<violation number="1" location=".github/workflows/release-branch.yml:50">
P2: `actions/dependency-review-action` is being run in a `workflow_dispatch` workflow, but no `base-ref`/`head-ref` are provided. The action’s docs call out `base-ref`/`head-ref` as the mechanism for non-PR event types, so consider setting them here to ensure the dependency comparison is done against the intended refs.</violation>
</file>

Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.

@jasonsaayman jasonsaayman merged commit 9aa34d5 into v1.x Mar 25, 2026
20 checks passed
@jasonsaayman jasonsaayman deleted the fix/update-release-branch-flow branch March 25, 2026 20:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

commit::fix The PR is related to a bugfix priority::high A high priority issue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant