chore(ci): update build pipeline to match concerto-docs#532
Merged
Conversation
- Upgrade Node.js from 14.x to 20.x - Upgrade Docusaurus from 3.7.0 to 3.10.0 - Update GitHub Actions: checkout@v4, setup-node@v4 - Switch from AWS access keys to OIDC role assumption - Replace jakejarvis/s3-sync-action with native aws s3 sync - Add security linting: syncpack + lockfile-lint - Pin all dependencies to exact versions (no caret ranges) - Add .nvmrc for consistent local development - Add @docusaurus/faster for improved build performance - Add timeout-minutes and environment to workflow Signed-off-by: Matt Roberts <code@rbrts.uk>
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
Update the techdocs build pipeline to match the modern concerto-docs pipeline configuration.
Changes
Flags
AWS_ROLEsecret before deployment will work. The workflow will fail on the "configure aws credentials" step until this is done.AWS_ACCESS_KEY_IDandAWS_SECRET_ACCESS_KEYsecrets can be removed after OIDC is configured.Testing
npm run lint:lockfile— No issues detectednpm run lint:deps— No issues foundnpm run build— Generated static files successfullyAuthor Checklist
mainfromchore/update-build-pipeline