Skip to content

chore: pin @evlog/cli to the 1.0 line - #15

Draft
HugoRCD wants to merge 1 commit into
mainfrom
chore/pin-cli-1.0
Draft

HugoRCD wants to merge 1 commit into
mainfrom
chore/pin-cli-1.0

Conversation

@HugoRCD

@HugoRCD HugoRCD commented Nov 17, 2026

Copy link
Copy Markdown
Member

Written by an AI agent on behalf of @HugoRCD. @HugoRCD has not reviewed it yet.

Draft: don't merge before @evlog/cli 1.0.0 is on npm (evlog 3.0 GA, 18 Jan 2027). It moves the action's default CLI from 0.8.0 to the 1.0 line. 1.0.0 isn't published yet (latest is 0.11.2, beta is 1.0.0-beta.2), so the pin is 1.0.0-beta.2 and CI runs the action against the real 1.0 contract now. On GA day, change the pin to 1.0.0 (Renovate will propose it as well), let CI pass, merge and tag. This PR replaces #10 (0.11.2).

action.yml version default and the README inputs table: 0.8.0 → 1.0.0-beta.2.

Same fixtures, both CLIs

node src/main.mjs locally, with INPUT_VERSION set and baseline: none, gate: true, min-score: 0, summary: true:

0.8.0 hono-app exit=0 score=100
0.8.0 nuxt-app exit=0 score=64
0.8.0 express-app exit=0 score=100
1.0.0-beta.2 hono-app exit=0 score=100
1.0.0-beta.2 nuxt-app exit=0 score=64
1.0.0-beta.2 express-app exit=0 score=100

GITHUB_OUTPUT is identical for every fixture. The job summary differs only in the footer version:

-<sub>[evlog map](https://evlog.dev/cli/map) v0.8.0 · ...
+<sub>[evlog map](https://evlog.dev/cli/map) v1.0.0-beta.2 · ...

The baseline jobs in test.yml cover the base-branch scan. That scan uses the same pinned CLI on both sides, so the 1.0 rule set (ruleSetVersion 3, up from 1 in 0.x) can't cause a baseline mismatch.

What changes in the map JSON between 0.x and 1.0 (diffed on the CLI side in evloghq/evlog#1124): grade, ignored and routes[].event are new, and nothing the action reads was removed or renamed. #14 makes the job summary pick up any check id the map reports, so 1.x can add checks without an action release.

npm test: 88 pass.

ELI5

The action runs a specific version of the evlog CLI. This switches it to the upcoming 1.0 version, after checking that the results are the same. It waits as a draft until 1.0.0 is published.

@coderabbitai

coderabbitai Bot commented Nov 17, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@github-actions

Copy link
Copy Markdown

Observability score · 64

needs work across 3 packages · unchanged against main · no regression

Package Score Δ Instrumented Partial Dark Gate
test/fixtures/express-app (express) 100 excellent 0 2 0 0 passed
test/fixtures/hono-app (hono) 100 excellent 0 2 0 0 passed
test/fixtures/nuxt-app (nuxt) 64 needs work 0 2 0 2 passed

Note

No min-score set. Add min-score: 64 to keep today's score from dropping.

Fix first (2)

evlog map v1.0.0-beta.2 · how the score works · what each check expects

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant