Skip to content

CI smoke test: line-counter README change on the reworked workflow - #53

Closed
blackcat wants to merge 6 commits into
mainfrom
MILAB-6910-ci-smoke-line-counter
Closed

blackcat wants to merge 6 commits into
mainfrom
MILAB-6910-ci-smoke-line-counter

Conversation

@blackcat

Copy link
Copy Markdown
Contributor

Smoke test of the reworked CI workflow from #52 against a package other than job-wrapper: a documentation-only change to line-counter with a patch changeset, to confirm the new Package tests / Package lint jobs and the test gate on build/publish leave the other packages green.

Based on the MILAB-6910-job-wrapper branch, so the wrapper commits show in the diff; only the last commit is this PR's own change. Not meant to be merged before #52.

🤖 Generated with Claude Code

pvyazankin and others added 6 commits September 18, 2026 17:41
The shared node-simple-pnpm workflow skips the test step unless it also
starts a Platforma backend (pl-start-for-tests), so no package test has
ever run in CI here. Add a dedicated job that runs the test script of every
package that has one, with Go and Docker, and make build/publish wait for it.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Add a lint job that installs golangci-lint v2.11.4 (the version used
locally) and runs the lint script of every package that has one; the
build/publish job waits for it.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
golangci-lint-action v8 has no install-only mode and lints a single working
directory itself, which fails at the repo root where there is no Go module.
Install the pinned binary with the official script and keep the per-package
loop.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Smoke test for the reworked CI workflow (Package tests / Package lint jobs
and the test gate on build/publish) against a package other than job-wrapper.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@notion-workspace

Copy link
Copy Markdown

@blackcat blackcat closed this Sep 21, 2026
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.

2 participants