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
Closed
Release sync: post-Apr-30 product changes into v2 (#638, CLI 2.111.0, Node 22)#643naveenku-jfrog wants to merge 4 commits into
naveenku-jfrog wants to merge 4 commits into
Conversation
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
force-pushed
the
sync/dev-into-v2-excluding-638
branch
from
August 3, 2026 07:23
cecb0dd to
f74dad5
Compare
Contributor
Author
|
Superseded by the reverse approach: merge v2 → dev first, then let the release pipeline merge dev → v2. |
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
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.
Summary
Brings all non-e2e product changes after 30 Apr 2026 from
devintov2for the upcoming release.Included (teammates’ product work)
#635/dfe055b16ead28#638/696faadExplicitly 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.shfile contents withdevso.jfrog-pipelines/pipelines.release.yml’sgit merge origin/devis conflict-free. This does not change extension task runtime behavior.After this merges,
v2tree ==devtree, so the release merge is a no-op and tagging/publishing can proceed.Test plan
exchangeOidcTokenViaRest,createCliDownloadAuthHandlers)2.111.0/ plugin2.14.2and Node 22 matrix changegit checkout v2 && git merge origin/dev— clean / already up to dateNEXT_VERSIONset