Repository navigation
feat: install the Limen CLI and log a job in as a bot - #1
Merged
Merged
Conversation
Downloads a Limen release, checks it against SHA256SUMS and its build provenance, puts only the limen binary on PATH, and optionally runs limen login --bot github_actions with a private LIMEN_HOME that the post step deletes. Plain Node 24, no dependencies, no build step.
CONTRIBUTING.md is the organization default. Removes a redundant mkdir and a pointless test line.
jfcmartins
marked this pull request as ready for review
November 2, 2026 00:10
jfcmartins
marked this pull request as draft
November 2, 2026 00:11
jfcmartins
marked this pull request as ready for review
November 2, 2026 00:11
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.
The first version of the action (ADR-0019 planned it: "a small GitHub Action wrapping the CLI comes later").
SHA256SUMSand the build provenance (gh attestation verify, pinned to limen-dev/limen'srelease.yml); fails closed.limenon PATH.proxy, runslimen login --bot github_actionsinto a privateLIMEN_HOMEthat the post step deletes.Verified: 18 unit tests; actionlint clean; install, checksum and provenance against the real v0.1.0-rc.1 release (archive, SHA256SUMS, attestation), served from a local server because that release is still a draft.
Unverified: the bot login against a real GitHub OIDC token and a real control plane (tests use a stub
limen); CI on this repo has not run yet (it starts when this PR is marked ready).Before tagging v0.1.0: publish a Limen release, then run the smoke workflow (
workflow_dispatch) and a real bot login against a test Limen. See RELEASING.md. Marketplace publishing is done by the owner from the release page.