Repository navigation
chore(release): 2.0.0 - #336
Merged
Merged
Conversation
Sets the version to 2.0.0, dates its changelog section, and points the npm install commands at its release. The changelog's 1.1.0 heading, which the merge of develop into master put after the Removed section of 2.0.0's entries, goes back above the entries that 1.1.0 released.
mindsers
force-pushed
the
release/2.0.0
branch
from
October 27, 2026 23:56
cde910a to
a927f17
Compare
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.
Summary
This pull request releases configfile 2.0.0. configfile is a command-line tool that installs your configuration files (dotfiles) and setup scripts from a git repository you own, and keeps every machine in sync with it.
The project uses git-flow: work is merged into
develop, and arelease/*branch brings it tomaster, which only holds released versions. A tag onmastertriggers.github/workflows/publish.yml, which builds the GitHub release (npm package, standalone binaries, checksums).All the code in this release was already reviewed in its own pull requests: this one only sets the version. It is a major version because some changes break existing setups; Upgrading from 1.x explains what to do.
Breaking changes
"method": "link". Copies changed on the machine are kept, and files changed on both sides are reported (Handle config files that tools rewrite through the links #297).configfile.module.jsoninstead ofsettings.json, so a module can deploy an app's ownsettings.json(Accept configfile.json as the module file name #299).initagain sets configfile up again from scratch, after asking (or with--force) (fix: "init --force" reuses the existing mirror instead of cloning again #331)."global"key are no longer read (feat!: stop reading the 0.3 list format and the "global" key #325).New
modules adoptadds files of the machine to a module (Adopt existing files into a module, and show drift in modules status #296)."when": modules and files for some systems or machine profiles only (Deploy modules or entries only on some OSes or machine profiles #302).post_updateandpost_initscripts (Run scripts after update and init (repository-level hooks) #317), andinitcan set up an empty repository (Create a new dotfiles repository from configfile #27).The full list is in the CHANGELOG.
Other Informations
Review order (one commit,
chore(release): 2.0.0)package.json:versionis 2.0.0.configfile --versionreads it.CHANGELOG.md: the entries since 1.1.0 move from Unreleased to[2.0.0] - 2026-10-28, and the compare links are updated. The[1.1.0]heading had been placed after 2.0.0's Removed section, so 2.0.0's new features were listed under 1.1.0. It now sits above the entries 1.1.0 released, and that section is identical to the one 1.1.0 shipped.README.md,docs/.../getting-started/installation.md,docs/.../guides/scripts-and-ci.md: the npm install commands point at the 2.0.0 release. The installation page says versions from 1.0 on are not on the npm registry yet.Merging: use a merge commit, not a squash, so that
masteranddevelopkeep a shared history.Tests: lint, type check, the docs build and the full test suite (811 tests) pass in CI on macOS and Linux, and the four standalone binaries build.
Manual test. Build the package from this branch and try it in a throwaway home folder. Your own
~/.configfilercand dotfiles are not touched, and nothing is pushed outside the temporary folder: