You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore: Use .nvmrc for Node version in CI/CD workflows and npm install in post-checkout hook (#92)
* Use .nvmrc for Node version in CI/CD workflows and npm install in post-checkout hook
- Update all workflow files (ci.yml, package.yml, deps.yml, copilot-setup-steps.yml) to use node-version-file: '.nvmrc' instead of hardcoded NODE_VERSION
- Remove NODE_VERSION environment variable from workflow files
- Change post-checkout hook from npm ci to npm install for local development
- All CI workflows continue to use npm ci as expected
* Update npm ci to npm install everywhere except CI workflow files
Changes:
- Updated CD workflow (package.yml) to use npm install
- Updated deps workflow (deps.yml) to use npm install
- Updated copilot-setup-steps workflow to use npm install
- Updated GitHub actions (npm-ci, build-vsix) to use npm install
- Updated Azure pipeline files (stable, pre-release) to use npm install
- Updated devcontainer files to use npm install in comments
- CI workflow files (ci.yml) continue to use npm ci as expected
This ensures npm ci is only used in CI environments where reproducible builds are critical, while npm install is used everywhere else for flexibility.
* Revert workflow files back to npm ci
CI workflow files should use npm ci for reproducible builds:
- package.yml (CD workflow)
- deps.yml (dependency checking)
- copilot-setup-steps.yml
Non-workflow files continue to use npm install:
- GitHub actions (npm-ci, build-vsix)
- Azure pipelines (stable, pre-release)
- Post-checkout git hook
- Devcontainer files
* Revert GitHub actions and Azure pipelines back to npm ci
All build and deployment pipelines should use npm ci for reproducible builds:
- .github/actions/npm-ci/action.yml
- .github/actions/build-vsix/action.yml
- build/azure-pipeline.stable.yml
- build/azure-pipeline.pre-release.yml
Only the post-checkout git hook and devcontainer files now use npm install.
* Update CONTRIBUTING.md to use npm install for local development
Changed all references from npm ci to npm install in documentation:
- Setup instructions
- Typical workflow example
- Local build instructions
This aligns with the change to use npm install for local development
while CI workflows continue to use npm ci for reproducible builds.
---------
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,7 @@ The `@deepnote/blocks` package is published on GitHub Packages. To install it, y
58
58
```
59
59
Replace `YOUR_TOKEN_HERE` with your actual token.
60
60
61
-
After completing these steps, you can install dependencies normally with `npm ci`. The project's `.npmrc` file is already configured to use GitHub Packages for the `@deepnote` scope.
61
+
After completing these steps, you can install dependencies normally with `npm install`. The project's `.npmrc` file is already configured to use GitHub Packages for the `@deepnote` scope.
62
62
63
63
On Apple Silicon, you will have to use system versions of `libsodium` and `libzmq` instead of the bundled ones:
0 commit comments