Skip to content

chore: sync develop with the v7.17.6 release - #23

Merged
ruleofcodedev merged 2 commits into
developfrom
master
Aug 8, 2026
Merged

chore: sync develop with the v7.17.6 release#23
ruleofcodedev merged 2 commits into
developfrom
master

Conversation

@ruleofcodedev

Copy link
Copy Markdown
Contributor

Brings the v7.17.6 version bump and CHANGELOG entry back to develop.

master is at 7.17.6 while develop still says 7.17.5, so the next release would branch from the wrong base — that has already caused one publish attempt from a stale tree.

No code change: the release commit is the only thing develop is missing.

ruleofcode.dev team and others added 2 commits August 8, 2026 16:07
Bumps package.json and hooks/installer VERSION to 7.17.6 and regenerates
the tracked .husky hooks. schemaVersion stays 2.

Ships what is already on develop:

- fix(laws): Git Hook Compliance called every hook of every Windows
  project non-executable — a violation `chmod +x` could not fix, since
  NTFS has no such bit. The mode now comes from the git index, which
  answers the same question on every platform, and only names git runs
  as hooks are judged. The real defect it was built to catch is kept:
  hooks committed at 100644 are not executable on a Linux clone.
- fix(deps): the lockfile pinned three transitive versions with
  high-severity advisories, so CI tested against them. Consumers were
  never exposed — a fresh install of the published package resolves the
  patched versions. package.json is unchanged.
- docs: the law card schema, and why `stack` and a `satisfiedBy` key are
  two axes rather than one vocabulary.

Gate: eslint 0, jest full suite, canary green (py100/ng136/node78).
Self-audit: exit 0.
chore(release): v7.17.6 — hook exec bit, clean lockfile, schema docs
@ruleofcodedev
ruleofcodedev merged commit 4abf3d3 into develop Aug 8, 2026
3 checks passed
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