Skip to content

Release sync: post-Apr-30 product changes into v2 (#638, CLI 2.111.0, Node 22) - #643

Closed
naveenku-jfrog wants to merge 4 commits into
v2from
sync/dev-into-v2-excluding-638
Closed

Release sync: post-Apr-30 product changes into v2 (#638, CLI 2.111.0, Node 22)#643
naveenku-jfrog wants to merge 4 commits into
v2from
sync/dev-into-v2-excluding-638

Conversation

@naveenku-jfrog

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

Copy link
Copy Markdown
Contributor

Summary

Brings all non-e2e product changes after 30 Apr 2026 from dev into v2 for the upcoming release.

Included (teammates’ product work)

Commit Author Change
#635 / dfe055b reshmifrog Node 22 in test matrix
16ead28 agrasth Default JFrog CLI → 2.111.0, pluginVersion → 2.14.2
#638 / 696faad Agrasth OIDC auth for ToolsInstaller CLI download

Explicitly not treated as release content

Naveen’s e2e/testing commits (#633, #641, and follow-ups). Those stay out of the product cherry-picks.

Pipeline hygiene (required)

One extra commit aligns e2e-plugin-tests.yml + trigger-ado-pipeline.sh file contents with dev so .jfrog-pipelines/pipelines.release.yml’s git merge origin/dev is conflict-free. This does not change extension task runtime behavior.

After this merges, v2 tree == dev tree, so the release merge is a no-op and tagging/publishing can proceed.

Test plan

  • PR diff includes OIDC helpers (exchangeOidcTokenViaRest, createCliDownloadAuthHandlers)
  • PR diff includes CLI 2.111.0 / plugin 2.14.2 and Node 22 matrix change
  • No unexpected task runtime changes beyond ToolsInstaller/utils
  • After merge: git checkout v2 && git merge origin/dev — clean / already up to date
  • Run release pipeline with NEXT_VERSION set

reshmifrog and others added 4 commits August 3, 2026 12:52
Copy e2e-plugin-tests.yml and trigger-ado-pipeline.sh from dev so the
release pipeline `git merge origin/dev` does not hit add/add conflicts.
No product/runtime behavior change to the extension tasks.

Co-authored-by: Cursor <cursoragent@cursor.com>
@naveenku-jfrog
naveenku-jfrog force-pushed the sync/dev-into-v2-excluding-638 branch from cecb0dd to f74dad5 Compare August 3, 2026 07:23
@naveenku-jfrog naveenku-jfrog changed the title Sync dev into v2 excluding #638 (OIDC ToolsInstaller) Release sync: post-Apr-30 product changes into v2 (#638, CLI 2.111.0, Node 22) Aug 3, 2026
@naveenku-jfrog

Copy link
Copy Markdown
Contributor Author

Superseded by the reverse approach: merge v2 → dev first, then let the release pipeline merge dev → v2.

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.

3 participants