Skip to content

ci(release): record each npm publish as a GitHub deployment#23

Merged
Aayam Bansal (aayambansal) merged 1 commit into
mainfrom
npm-deployment-records
Jul 5, 2026
Merged

ci(release): record each npm publish as a GitHub deployment#23
Aayam Bansal (aayambansal) merged 1 commit into
mainfrom
npm-deployment-records

Conversation

@aayambansal

Copy link
Copy Markdown
Member

Adds a deployment job 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/openscience version). The repo's Deployments sidebar then shows npm releases alongside the Vercel Production/Preview deployments.

Workflow-only change; actionlint runs in CI.

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.
@vercel

vercel Bot commented Jul 5, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
openscience Ready Ready Preview, Comment Jul 5, 2026 9:04am

Request Review

@aayambansal Aayam Bansal (aayambansal) merged commit abf633e into main Jul 5, 2026
9 checks passed
@aayambansal Aayam Bansal (aayambansal) deleted the npm-deployment-records branch July 5, 2026 09:05
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)
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.

1 participant