Repository navigation
Remove package.json version fields, bump Fjell deps, and simplify npm publish workflow
Summary
This release makes three focused changes tracked in the repository: package metadata cleanup (package.json version lines removed), patch bumps of Fjell peer/runtime dependencies, and a simplification of the GitHub npm-publish workflow by removing the explicit npm update step.
Package metadata
- Remove package.json version entries (deleted the two version lines
"4.4.75-dev.0"and"4.4.75") in package.json (see commit 55c85ae). The surrounding fields (e.g.,type,keywords) were left unchanged. (commit: 55c85ae)
Dependency updates
- Bump @fjell/lib from
^4.4.80to^4.4.81in package.json. (commit: feb8f10) - Bump @fjell/logging from
^4.4.60to^4.4.62in package.json. (commit: feb8f10) - Bump @fjell/registry from
^4.4.77to^4.4.79in package.json. (commit: feb8f10)
Reference: the dependency version changes are recorded in package.json (commit: feb8f10).
CI / Workflow changes
- Remove the
Update npmstep (npm install -g npm@latest) from the GitHub Actions npm publish workflow (.github/workflows/npm-publish.yml). The remaining workflow steps (npm ciandnpm publish) were left unchanged in that commit. (commit: fd737c3)
Files changed
- package.json — removed version lines; updated Fjell dependency patch versions. (commits: 55c85ae, feb8f10)
- .github/workflows/npm-publish.yml — removed the explicit
npmupdate step. (commit: fd737c3)
Upgrade / operational notes
- Consumers of the repository should note that package.json no longer contains the two explicit version lines removed in this change — versioning may be managed elsewhere in the release process.
- The npm-publish workflow no longer force-updates npm via
npm install -g npm@latest; the workflow will run with the runner's npm as-is unless other steps set a different version.