Use shared workflow for JS+PY release#204
Open
David Elner (delner) wants to merge 1 commit into
Open
Conversation
Braintrust eval report
|
David Elner (delner)
force-pushed
the
ci/release_shared_action
branch
3 times, most recently
from
July 16, 2026 03:55
429951e to
2841f76
Compare
David Elner (delner)
temporarily deployed
to
publish-dry-run
July 16, 2026 03:57 — with
GitHub Actions
Inactive
David Elner (delner)
had a problem deploying
to
publish-dry-run
July 16, 2026 03:57 — with
GitHub Actions
Failure
David Elner (delner)
force-pushed
the
ci/release_shared_action
branch
from
July 16, 2026 15:26
2841f76 to
c0325c6
Compare
David Elner (delner)
temporarily deployed
to
publish-dry-run
July 16, 2026 15:28 — with
GitHub Actions
Inactive
David Elner (delner)
temporarily deployed
to
publish-dry-run
July 16, 2026 15:28 — with
GitHub Actions
Inactive
David Elner (delner)
force-pushed
the
ci/release_shared_action
branch
from
July 16, 2026 18:43
c0325c6 to
75242a6
Compare
David Elner (delner)
requested a deployment
to
publish-dry-run
July 16, 2026 18:45 — with
GitHub Actions
Waiting
David Elner (delner)
requested a deployment
to
publish-dry-run
July 16, 2026 18:45 — with
GitHub Actions
Waiting
David Elner (delner)
force-pushed
the
ci/release_shared_action
branch
from
July 17, 2026 02:43
75242a6 to
76c31ac
Compare
David Elner (delner)
temporarily deployed
to
publish-dry-run
July 17, 2026 02:46 — with
GitHub Actions
Inactive
David Elner (delner)
temporarily deployed
to
publish-dry-run
July 17, 2026 02:46 — with
GitHub Actions
Inactive
David Elner (delner)
force-pushed
the
ci/release_shared_action
branch
from
July 17, 2026 02:57
76c31ac to
6f1d066
Compare
David Elner (delner)
temporarily deployed
to
publish-dry-run
July 17, 2026 02:59 — with
GitHub Actions
Inactive
David Elner (delner)
force-pushed
the
ci/release_shared_action
branch
from
July 17, 2026 03:04
6f1d066 to
6814b51
Compare
David Elner (delner)
marked this pull request as ready for review
July 17, 2026 03:05
Abhijeet Prasad (AbhiPrasad)
approved these changes
Jul 17, 2026
There was a problem hiding this comment.
don't we still need two different files for trusted publishing? Or is it that both python and js point to the same file?
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.
Replaces the separate
publish-js.yaml/publish-py.yamlworkflows and their dispatcher with a singlepublish.yamlthat releases the npm and PyPIautoevalspackages together, at one shared version, behind one approval gate . The workflow is built on the shared release actions frombraintrustdata/sdk-actions.What changes
configure → validate → packper lane, one sharedrequest-approval, then a gatedship-packageper lane.Benefits
fails before the gate, neither ships.