Repository navigation
Require devlanes 0.11.0 and set up the runner with devlanes setup - #6
Merged
Merged
Conversation
Mira PR WalkthroughRaises the action's minimum and default devlanes version to 0.11.0 and replaces the removed Confidence: 4/5 ◉◉◉◉○ Safe with minor checks
16 files reviewed
|
arthurfiorette
marked this pull request as ready for review
November 1, 2026 20:55
devlanes 0.8.0 runs relative paths from the project file's folder; the fixtures still named them from the repository root. The regenerated pnpm lockfile is formatted as Biome expects.
This was referenced Nov 1, 2026
…E_PROJECT 0.11.0 installs the hosts helper on GitHub's runners and no longer lets one lane's exported DEVLANES_PROJECT pin the next project in the job.
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.
devlanes 0.10.0 (devlanes-run/devlanes#102) removed
devlanes certs trustand addeddevlanes setup. 0.11.0 (#107, #109) fixed two things this action ran into:/etc/sudoers.d/runneralready failsvisudo;DEVLANES_PROJECTpinned the next project in the same job to the wrong project. Lanes now export it asDEVLANES_LANE_PROJECT.The action now requires 0.11.0, so it never runs
certs trustand never depends on the old variable.versioninput or a lockfile/package.jsonpin older than that fails the step with the file named.devlanes setup --yes. It still installscertutiland still writestls.trust: [system, chrome]unless the workflow'sconfigsetstls.trust. A failure is still only a warning.hosts-fileon Linux. The action writes this into the user config before the daemon starts, instead of passing--hosts:truewriteshostnames.hosts_file: always.falsewritesnever, sosetupdoesn't install the helper on its own.autowrites nothing, sosetupinstalls the helper only when*.localhostdoesn't resolve on the runner, for example in a container job.hostnames.hosts_filein the workflow'sconfigstill wins.hosts-file: truewithtrust: false. This still runssetup, which also trusts the CA, as the old helper install did. The README says so.export-env. The README listsDEVLANES_LANE_PROJECT, and the e2e check asserts it. The e2e check's URL pattern now matches lane domains without a dash, which devlanes has used since 0.9.0.hosts-helperjob runs the action withhosts-file: trueand checks the helper is installed anddevlanes setup --checkpasses.dist/is rebuilt.Verified locally
pnpm lint-ci,pnpm test-types,pnpm test(76 passed) andpnpm buildall pass.Agent and model: OpenCode / Claude Opus 5.5.