Skip to content

Sync product changes from dev into v2 for release (single commit) - #645

Merged
naveenku-jfrog merged 1 commit into
v2from
chore/sync-into-v2-single
Aug 3, 2026
Merged

Sync product changes from dev into v2 for release (single commit)#645
naveenku-jfrog merged 1 commit into
v2from
chore/sync-into-v2-single

Conversation

@naveenku-jfrog

@naveenku-jfrog naveenku-jfrog commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Summary

Brings the latest product changes into v2 in a single commit so the release pipeline can build and publish the next version.

Included:

  • Authenticate the JFrog CLI download for OIDC service connections in JFrogToolsInstaller (fixes HTTP 401 when the CLI is not already cached on the agent).
  • Bump default JFrog CLI to 2.111.0 and pluginVersion to 2.14.2.
  • Add Node 22 to the test matrix.

The e2e-plugin-tests.yml and trigger-ado-pipeline.sh files are aligned so the release step git merge origin/dev stays conflict-free.

Verification

  • Branch content is identical to dev.
  • Simulated release merge v2 <- dev: clean.

Test plan

  • Diff includes the OIDC ToolsInstaller auth change, CLI 2.111.0 / plugin 2.14.2, and the Node 22 matrix entry.
  • After merge, from v2: git merge origin/dev is clean / already up to date.
  • Run the release pipeline with NEXT_VERSION set.

Brings the post-2026-04-30 non-e2e product work onto v2 so the release
pipeline can build and publish the new version:

- #638: authenticate JFrog CLI download for OIDC service connections
        (JFrogToolsInstaller)
- Default JFrog CLI 2.111.0 / pluginVersion 2.14.2
- Node 22 in the test matrix (RTECO-813)

Also aligns e2e-plugin-tests.yml and trigger-ado-pipeline.sh with dev so
the release step `git merge origin/dev` is conflict-free. No change to
extension task runtime behavior beyond the items above.

Co-authored-by: Cursor <cursoragent@cursor.com>
@naveenku-jfrog
naveenku-jfrog merged commit 794be1d into v2 Aug 3, 2026
13 of 14 checks passed
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