Repository navigation
feat(cloudsmith): add CI and switch to Cloudsmith for installs - #1
Merged
Merged
Conversation
- New .github/workflows/ci.yml, modeled on fw-state's: checkout, setup node, authenticate with Cloudsmith via OIDC (cloudsmith-io/cloudsmith-cli-action), then npm ci + build. This repo previously had no GitHub Actions workflow at all. - .npmrc: global registry= now points at Cloudsmith (npm.artifacts.hyland.dev/cic-unified-shared-libs), authenticated via CLOUDSMITH_API_KEY instead of registry.npmjs.org. - package.json: pin minimatch/@types/minimatch/tslib to the exact versions the previous lockfile had. A full re-resolution against Cloudsmith otherwise lets these drift to newer majors (minimatch's modern .d.ts syntax breaks this repo's TypeScript 2.9.2 compiler; newer tslib's package.json exports map breaks rollup-plugin-typescript2). - package-lock.json regenerated against Cloudsmith (same resolved versions as before, new registry). Verified locally: clean install resolves every package through Cloudsmith, and npm run build produces the same dist/ output as before.
Member
Author
|
Added a follow-up commit switching this repo's |
raiseandfall
marked this pull request as ready for review
October 12, 2026 21:03
Adds the Semantic Release step to the CI workflow, grants contents: write permission for tagging/releasing, and adds a release.config.js with the same plugin pipeline used in web-shared-models (commit-analyzer, release-notes-generator, changelog, npm, github, git).
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
Adds a GitHub Actions CI workflow (this repo had none) and migrates installs from the private npm registry (registry.npmjs.org) to Cloudsmith. Modeled directly on
learningmachine/fw-state's setup — same situation (scoped @learningmachine package, no publish automation, manual npm publish).Changes
.github/workflows/ci.yml: checkout → setup node → Cloudsmith OIDC auth (cloudsmith-io/cloudsmith-cli-action) →npm ci→npm run build --if-present(swapped fornpm run testsince this repo has no test script, unlike fw-state)..npmrc: globalregistry=now points at Cloudsmith (npm.artifacts.hyland.dev/cic-unified-shared-libs), authenticated viaCLOUDSMITH_API_KEY.package.json: addedoverridespinningminimatchand@types/minimatch, and pinned the directtslibdependency, to the exact versions the previous lockfile had. A full re-resolution against Cloudsmith otherwise lets these drift to newer majors that break this repo's build (modern minimatch.d.tssyntax breaks the ancient TypeScript 2.9.2 compiler; newer tslib'sexportsmap breaksrollup-plugin-typescript2's way of loading it).package-lock.jsonregenerated against Cloudsmith — same resolved versions as before, just a different registry.Semantic Releasestep in.github/workflows/ci.yml, mirroringweb-shared-models's setup (cycjimmy/semantic-release-action@v6, same branch pattern withmasterswapped in formain). Bumped workflowpermissions.contentstowriteand added a job-levelGITHUB_TOKENenv, both required for the release step.release.config.jswith the same plugin pipeline asweb-shared-models(commit-analyzer,release-notes-generator,changelog,npm,github,git).Requirements
CLOUDSMITH_NAMESPACErepo/org variable must be set.locals-learningmachine.tf— PR pending there too, slug:learningmachine-caching).Notes
web-shared-modelsas-is, including its existing gap:@semantic-release/changelogand@semantic-release/gitare not incycjimmy/semantic-release-action's default plugin set and would normally needextra_pluginsdeclared on the step. Left unchanged intentionally to match the reference setup.Verification
Clean install resolves every package through Cloudsmith (confirmed via
package-lock.json), andnpm run buildproduces the samedist/output as before the change.