chore(release): 1.1.0

[mindsers]

Release branch for configfile 1.1.0, following git-flow: develop as of #320, with the version set. Merging this into master and pushing the 1.1.0 tag on the merge commit publishes the release (.github/workflows/publish.yml).

What's in 1.1.0

The full list is in the CHANGELOG. The main changes:

• Standalone binaries for macOS and Linux (x64 and arm64), with an install script: curl -fsSL https://docs.configfile.sh/install.sh | sh (Standalone binaries and a one-line installer for new machines #301). This is the first release built by the new binaries job.
• Module deployment scripts: pre_deploy, post_deploy, pre_undeploy, post_undeploy (Post-deploy hooks per module #298).
• Script environment variables: CONFIGFILE_REPO, CONFIGFILE_SCRIPT, CONFIGFILE_OS (Give scripts the repository path and context in environment variables #295).
• A JSON Schema for settings.json, and the documentation site docs.configfile.sh.
• Locking fixes: update and init wait for deployments (update and init don't take the lock that deploy and undeploy use #313), and the lock is safer.

Changes on this branch

• chore(release): 1.1.0:
  • sets version to 1.1.0 in package.json;
  • moves the Unreleased changelog entries under [1.1.0] - 2026-10-14 and adds its link;
  • points the npm install commands (README, installation page, CI guide) at the 1.1.0 release;
  • says "Versions 1.x are not on the npm registry yet", since NPM_PUBLISH is not set.
• A merge of master that keeps develop's content (git merge -s ours):
  • 1.0.0 and its hotfixes (chore(release): 1.0.0 #291, fix: keep the configfile command when publishing to npm #293, ci(publish): publish GitHub releases, make npm publishing opt-in #294) were squash-merged into master, so master shares no history with develop after 0.3.1, and a plain merge conflicts on 25 files.
  • I checked that every file version on master also appears in develop's history, where later work replaced it. The merge records master as merged without taking its content, so this PR merges cleanly.
  • Merge this PR with a merge commit, not a squash, or master and develop drift apart again.

Checks

• Lint, type check and the docs build pass.
• The full test suite passed (516 tests), but tests/git.test.ts:160 ("stops waiting on time…") failed 2 times in 4 full runs on my machine. It passed every time on its own. It is a timing test, unrelated to this branch.
• The built CLI reports 1.1.0.

After merging

1. Tag the merge commit on master with 1.1.0 and push the tag.
2. On the release, check:
   • four configfile-*.tar.gz, configfile-1.1.0.tgz, SHA256SUMS, and attestations;
   • then curl -fsSL https://docs.configfile.sh/install.sh | sh on a clean machine.
3. Merge master back into develop.
4. Update the Homebrew formula in mindsers/tap to 1.1.0, if it is not automated.