ci(release): record each npm publish as a GitHub deployment#23
Merged
Conversation
Every release now creates a deployment in an 'npm' environment (marked successful, linking to the published package version) so the Deployments sidebar shows npm releases next to the Vercel Production/Preview entries.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Aayam Bansal (aayambansal)
added a commit
that referenced
this pull request
Jul 7, 2026
… update() persists (#125) - Managed (enterprise /etc) config now merges LAST, after the dashboard-synced config, so an admin policy can't be silently overridden by a per-user dashboard value (the synced layer previously merged after managed). (#18a) - A failed well-known remote-config fetch no longer rejects Config.get() and bricks the CLI — it's the lowest-precedence base layer, so log and continue (mirroring the synced-config resilience). (#23) - Config.update() writes to a project config READ path (projectConfigFile) instead of <Instance.directory>/config.json, which the loader only reads as the GLOBAL config — so PATCH /config appeared to save but vanished on the next reload. (#34)
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.
Adds a
deploymentjob to the release workflow: after a successful publish it creates a GitHub deployment in an npm environment (state: success, environment URL pointing at the published@synsci/openscienceversion). The repo's Deployments sidebar then shows npm releases alongside the Vercel Production/Preview deployments.Workflow-only change; actionlint runs in CI.