Skip to content

fix: ship the update workflow in the package - #64

Merged
vannt-dev merged 1 commit into
mainfrom
fix/ship-update-workflow
Oct 13, 2026
Merged

vannt-dev merged 1 commit into
mainfrom
fix/ship-update-workflow

Conversation

@vannt-dev

Copy link
Copy Markdown
Owner

Merge this before releasing 0.9.0 (release PR #63). The bug is in #62, which is on main and not released yet.

The bug

modules.autoupdate: true with github.workflows.source: local gives the repository its own copy of repokeeper-update.yml. The copy is read from the installed package, and the file was not in the package's files. It worked from a checkout of this repository, which is where #62 was tried, and fails from npm:

$ repokeeper init
using the .repokeeper.yml that is already here
Error: ENOENT: no such file or directory, open '…/node_modules/repokeeper/.github/workflows/repokeeper-update.yml'

Repositories that call the workflows from vannt-dev/repokeeper (the default) are not affected: they never read the file from the package.

The fix

  • package.json: .github/workflows/repokeeper-update.yml added to files.
  • test/package-files.test.ts: every reusable workflow listWorkflows() names must be covered by files. It failed with [ 'repokeeper-update.yml' ] before the change.

Tested

  • The new test, seen failing first. typecheck, lint, 435 tests, build, npm run standard.
  • The package itself, before and after: npm pack with package.json as on main and as on this branch, each tarball installed in an empty project and run in a new repository whose .repokeeper.yml has modules.autoupdate: true and github.workflows.source: local. Before: the ENOENT above, nothing written. After: init applies the standard and .github/workflows/ holds repokeeper-autoupdate.yml and the copy repokeeper-update.yml.

No changelog entry is needed for users: the feature it repairs has not been released.

modules.autoupdate with `github.workflows.source: local` gives the repository
its own copy of repokeeper-update.yml, read from the installed package. The
file was missing from the package's `files`, so that copy could not be read:
it worked from a checkout of this repository and would have failed from npm.

A test now checks that every reusable workflow a repository can be given a
copy of is covered by `files`.
@vannt-dev
vannt-dev merged commit 47d4e27 into main Oct 13, 2026
5 checks passed
@vannt-dev
vannt-dev deleted the fix/ship-update-workflow branch October 13, 2026 14:57
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