On next beyond main. One unit: vaultik now uses the canonical lint config from prompts (#90). It replaces the deprecated gomodguard with gomodguard_v2, so lint no longer prints deprecation warnings. It also turns on the depguard rule that keeps test-support code out of the shipped binary. The one difference from canonical is that this rule also names vaultik's own test-only package, internal/storage/faultstore. No product code changed, and the new config found nothing to fix.
To merge.make check is green on the head (d24f5dc). Merging updates main only: no tag, no release, no deploy. Gitea may show next one commit behind main. That commit is your merge of #114, whose content is already here, so the merge is clean.
Waiting on you, outside this PR. The 1.0 scope and any tag (#125), daemon mode (#94), and the CI runner (#133).
Model: opus-5-5
**On `next` beyond `main`.** One unit: vaultik now uses the canonical lint config from `prompts` (https://git.eeqj.de/sneak/vaultik/issues/90). It replaces the deprecated `gomodguard` with `gomodguard_v2`, so lint no longer prints deprecation warnings. It also turns on the `depguard` rule that keeps test-support code out of the shipped binary. The one difference from canonical is that this rule also names vaultik's own test-only package, `internal/storage/faultstore`. No product code changed, and the new config found nothing to fix.
**To merge.** `make check` is green on the head (`d24f5dc`). Merging updates `main` only: no tag, no release, no deploy. Gitea may show `next` one commit behind `main`. That commit is your merge of https://git.eeqj.de/sneak/vaultik/pulls/114, whose content is already here, so the merge is clean.
**Waiting on you, outside this PR.** The 1.0 scope and any tag (https://git.eeqj.de/sneak/vaultik/issues/125), daemon mode (https://git.eeqj.de/sneak/vaultik/issues/94), and the CI runner (https://git.eeqj.de/sneak/vaultik/issues/133).
Model: opus-5-5
The lint config is now the canonical file from `prompts`, which replaces the deprecated `gomodguard` with `gomodguard_v2`, so lint prints no deprecation warnings. It also turns on the `depguard` `test-support` rule. The one difference from canonical is that the deny list names vaultik's own test-only package `internal/storage/faultstore`, so shipped code cannot import it. The new config found nothing to fix in the source.
Issues and PRs that pin the old `.golangci.yml` sha256 as an untouched-file check need the new one: `7122fcf0dd0ea57441374f98ebd98bb3da23decb67f9209fee5175170838fbd1`.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
On
nextbeyondmain. One unit: vaultik now uses the canonical lint config fromprompts(#90). It replaces the deprecatedgomodguardwithgomodguard_v2, so lint no longer prints deprecation warnings. It also turns on thedepguardrule that keeps test-support code out of the shipped binary. The one difference from canonical is that this rule also names vaultik's own test-only package,internal/storage/faultstore. No product code changed, and the new config found nothing to fix.To merge.
make checkis green on the head (d24f5dc). Merging updatesmainonly: no tag, no release, no deploy. Gitea may shownextone commit behindmain. That commit is your merge of #114, whose content is already here, so the merge is clean.Waiting on you, outside this PR. The 1.0 scope and any tag (#125), daemon mode (#94), and the CI runner (#133).
Model: opus-5-5
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.