Skip to content

chore(release): 2.0.0 - #336

Merged
mindsers merged 1 commit into
masterfrom
release/2.0.0
Oct 28, 2026
Merged

mindsers merged 1 commit into
masterfrom
release/2.0.0

Conversation

@mindsers

@mindsers mindsers commented Oct 27, 2026 •

Copy link
Copy Markdown
Owner

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 a release/* branch brings it to master, which only holds released versions. A tag on master triggers .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

New

The full list is in the CHANGELOG.

Other Informations

Review order (one commit, chore(release): 2.0.0)

  1. package.json: version is 2.0.0. configfile --version reads it.
  2. 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.
  3. 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 master and develop keep 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 ~/.configfilerc and dotfiles are not touched, and nothing is pushed outside the temporary folder:

pnpm install && pnpm pack                       # configfile-2.0.0.tgz
(
  export HOME="$(mktemp -d)" PREFIX="$(mktemp -d)"
  npm install --global --prefix "$PREFIX" ./configfile-2.0.0.tgz
  export PATH="$PREFIX/bin:$PATH"; cd "$HOME"
  configfile --version                          # 2.0.0
  git config --global user.name Test; git config --global user.email test@example.com
  git init -q --bare dotfiles.git
  configfile init --repo "$HOME/dotfiles.git" --working-copy "$HOME/dotfiles" --new-repository </dev/null
  echo 'export EDITOR=vi' > .zshrc
  configfile modules adopt ~/.zshrc --module zsh </dev/null
  configfile modules status zsh                 # ~/.zshrc (copied)
  configfile init </dev/null                    # asks for --force: already set up
)

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
mindsers merged commit 3a2dfb9 into master Oct 28, 2026
11 checks passed
@mindsers
mindsers deleted the release/2.0.0 branch October 28, 2026 00:06
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