Repository navigation
chore(ci): enable yarn hardened mode and immutable installs (API-476) - #6915
Merged
Merged
Conversation
Contributor
No code generatedIf you believe code should've been generated, please, report the issue. π Benchmark resultsBenchmarks performed on the method using a mock server, the results might not reflect the real-world performance.
|
Summary by Aikido
β‘ Enhancements
π§ Refactors
|
β¦uildLanguages (API-476)
MarioAlexandruDan
force-pushed
the
chore/api-476-yarn-hardened-installs
branch
from
August 18, 2026 14:32
4058b85 to
a3c5c4c
Compare
MarioAlexandruDan
marked this pull request as ready for review
August 18, 2026 14:32
|
π Deployed on https://6a8595126c42a155160687f7--api-clients-automation.netlify.app |
eric-zaharia
approved these changes
Aug 19, 2026
MarioAlexandruDan
enabled auto-merge (squash)
August 19, 2026 11:20
algolia-api-clients-automation-bot Bot
added a commit
to algolia/algoliasearch-client-javascript
that referenced
this pull request
Aug 19, 2026
β¦ (generated) algolia/api-clients-automation#6915 Co-authored-by: Mario-Alexandru Dan <marioalexandrudan@gmail.com>
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.
π§ What and Why
π JIRA Ticket: API-476
Changes included:
Turn on yarn hardened mode and remove the explicit immutable install opt-outs on the two CI installs in the setup action (
.github/actions/setup/action.yml:49and:110). Immutable installs are already yarn's default when CI is set, the old lines were opting out of it.The post codegen step that updates
yarn.lockkeeps immutable installs off since it intentionally rewrites the lockfile, but now runs with hardened mode (.github/workflows/check.yml:223).Also enable hardened mode on the post codegen install spawned by
yarn cli build(scripts/buildLanguages.ts:57), CI only so local builds keep their speed.Same treatment for the remaining CI install sites found on a full sweep: CTS runs and generation (
scripts/cts/runCts.ts:92,scripts/cts/generate.ts:31), docs generation (scripts/docs/generate.ts:32) and the website build (scripts/website/build.sh:11), all gated on CI so local runs are unchanged. The TS sites share aYARN_HARDENED_MODE_PREFIXconstant fromscripts/common.ts.Behavior note: with the root install strictly immutable, a PR that leaves a lockfile desynced now fails at the Setup step across the job matrix instead of being silently auto-repaired. That is the intent of the change, but the first dependency bump after merge will surface it as multiple red jobs.
Hardened mode also on the standalone JS client release workflow install (
clients/algoliasearch-client-javascript/.github/workflows/release.yml:30). It runs on push where yarn's default leaves hardened mode off, and it feeds the npm publish.π§ͺ Test