Dual-publish to npm and GitHub Packages on release

[delthas]

What

Dual-publishes @scality/cloudserverclient to both npmjs and GitHub Packages on release, and attests the published artifact. Mirrors the dual-publish + attestation model of @scality/hdclient and @scality/arsenal (ARSN-605). Today only a stale 1.0.0 sits on GitHub Packages.

How — build once, publish the same tarball to both

• build — after the branch / version / tag / release guards: yarn build → npm pack → generate a signed GitHub build-provenance attestation for the tarball (actions/attest-build-provenance) → upload the .tgz as the artifact.
• publish-npm — download the tarball, npm publish *.tgz --provenance --tag latest via OIDC trusted publishing (no token). npm-native provenance shows on npmjs.
• publish-github — download the same tarball, npm publish *.tgz --tag latest with the built-in GITHUB_TOKEN.
• create-release — GitHub release + tag once both publishes succeed, linking both packages.

Building/packing once and publishing the same tarball means a single attestation — gh attestation verify <tgz> --repo scality/cloudserverclient — covers whatever lands in either registry, plus npm-native provenance on npmjs.

Hardening

• Release only from development/* or hotfix/*.
• Fail early if the version's git tag or GitHub release already exists.
• Each publish skips if that version is already on that registry, so a partial dual-publish can be re-run cleanly instead of hitting E409.
• Least-privilege permissions per job (attestations: write on build, packages: write on publish-github, id-token: write on build/publish-npm).

package.json

• Removed the publishConfig.registry pin (kept access: public); each job sets its own target registry via setup-node (matches hdclient/arsenal). Scoped name, types, files already present.

Why

Step toward migrating Scality Node consumers (cloudserver, backbeat, s3utils, Zenko) to pull @scality/* from GitHub Packages (ARSN-605). The @scality:registry redirect applies to the whole scope, so every @scality/* dependency must be available on GitHub Packages; cloudserverclient is the main gap.

Notes

• Version stays committed / manually bumped — no auto-stamp.
• Provenance: npm-native --provenance is npmjs-only, so the GitHub Packages copy is instead covered by the GitHub build-provenance attestation (both registries get the same attested tarball).
• Out of scope: migrating consumers; retro-publishing old versions (new releases only, per S3C-9725).

Issue: CLDSRVCLT-16

[bert-e]

Hello delthas,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options

name	description	privileged	authored
/after_pull_request	Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval	Bypass the pull request author's approval	⭐
/bypass_build_status	Bypass the build and test status	⭐
/bypass_commit_size	Bypass the check on the size of the changeset TBA	⭐
/bypass_incompatible_branch	Bypass the check on the source branch prefix	⭐
/bypass_jira_check	Bypass the Jira issue check	⭐
/bypass_peer_approval	Bypass the pull request peers' approval	⭐
/bypass_leader_approval	Bypass the pull request leaders' approval	⭐
/approve	Instruct Bert-E that the author has approved the pull request.		✍️
/create_pull_requests	Allow the creation of integration pull requests.
/create_integration_branches	Allow the creation of integration branches.
/no_octopus	Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity	Change review acceptance criteria from one reviewer at least to all reviewers
/wait	Instruct Bert-E not to run until further notice.

Available commands

name	description	privileged
/help	Print Bert-E's manual in the pull request.
/status	Print Bert-E's current status in the pull request TBA
/clear	Remove all comments from Bert-E from the history TBA
/retry	Re-start a fresh build TBA
/build	Re-start a fresh build TBA
/force_reset	Delete integration branches & pull requests, and restart merge process from the beginning.
/reset	Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• 2 peers

[SylvainSenechal]

are you sure we wanna do this ? Why do we want to release on github too ? For this project we said we wanted to install from npm only 🤔

[delthas]

are you sure we wanna do this ? Why do we want to release on github too ? For this project we said we wanted to install from npm only 🤔

See the "Why": the end goal is to be able to consume JS packages from package registries rather than from Git (enabling us, later, to drop bump commits entirely). To do this we'll tell JS that all packages from "scality/" are stored in the Github package registry. This is namespace/org-wide redirect, so if we do this eg in cloudserver to pull arsenal from the Github package registry, it will also want to pull cloudserverclient from the Github package registry. Hence the need to dual publish.

[delthas]

Added Github packages attestation

[delthas]

/approve

[bert-e]

I have successfully merged the changeset of this pull request
into targetted development branches:

• ✔️ development/1.0

Please check the status of the associated issue CLDSRVCLT-16.

Goodbye delthas.

The following options are set: approve