Skip to content

Releases: Studnicky/mnemotek

@studnicky/git-flow@0.4.0

Choose a tag to compare

@github-actions github-actions released this 30 Jul 01:52
d36a231

Minor Changes

  • #28 2b390a9 Thanks @Studnicky! - Adds five new Mnemotek-based packages: @studnicky/memoria (agent-native
    dotfile manager — adopt/apply/diff/status/verify/bootstrap/secrets/catalog/
    doctor), @studnicky/git-hooks (core.hooksPath dispatcher plus bundled
    protected-branch, large-file, and secret-scan pre-commit checks),
    @studnicky/git-stack (thin passthrough to the gh-stack CLI extension),
    @studnicky/github-release (gh release create wrapper), and
    @studnicky/labels-sync (GitHub label pull/push, add-only and dry-run by
    default). None depend on a graph server, agent-orchestration proxy, or live
    external API beyond the already-authenticated git/gh CLIs.

    @studnicky/git-flow gains cleanup (merged-branch pruning) and
    milestone (WIP checkpoint commits, no Jira coupling) commands, and fixes
    a real concurrency bug in GitPrimitives.acquireLock: the previous
    existsSync-then-writeFileSync check let two concurrent invocations both
    believe they held the lock. Lock acquisition is now exclusive-create with
    stale-pid reclaim.

    @studnicky/config-standards gains ten new rules (editorconfig,
    vscode, prettier, style-drift, version-pin, envcheck,
    codeowners, devcontainer, issue-templates, template-sync) alongside
    the existing .gitignore/package.json checks, plus its own corrected
    lock file for fix and an atomic write helper used across every new and
    existing fixer.

@studnicky/config-standards@0.2.0

Choose a tag to compare

@github-actions github-actions released this 30 Jul 01:52
d36a231

Minor Changes

  • #28 2b390a9 Thanks @Studnicky! - Adds five new Mnemotek-based packages: @studnicky/memoria (agent-native
    dotfile manager — adopt/apply/diff/status/verify/bootstrap/secrets/catalog/
    doctor), @studnicky/git-hooks (core.hooksPath dispatcher plus bundled
    protected-branch, large-file, and secret-scan pre-commit checks),
    @studnicky/git-stack (thin passthrough to the gh-stack CLI extension),
    @studnicky/github-release (gh release create wrapper), and
    @studnicky/labels-sync (GitHub label pull/push, add-only and dry-run by
    default). None depend on a graph server, agent-orchestration proxy, or live
    external API beyond the already-authenticated git/gh CLIs.

    @studnicky/git-flow gains cleanup (merged-branch pruning) and
    milestone (WIP checkpoint commits, no Jira coupling) commands, and fixes
    a real concurrency bug in GitPrimitives.acquireLock: the previous
    existsSync-then-writeFileSync check let two concurrent invocations both
    believe they held the lock. Lock acquisition is now exclusive-create with
    stale-pid reclaim.

    @studnicky/config-standards gains ten new rules (editorconfig,
    vscode, prettier, style-drift, version-pin, envcheck,
    codeowners, devcontainer, issue-templates, template-sync) alongside
    the existing .gitignore/package.json checks, plus its own corrected
    lock file for fix and an atomic write helper used across every new and
    existing fixer.

@studnicky/git-flow@0.3.0

Choose a tag to compare

@github-actions github-actions released this 29 Jul 14:18
ff1f611

Minor Changes

  • #23 f6423e2 Thanks @Studnicky! - feature/release/hotfix now adapt to the target repository's actual merge settings instead of hardcoding a strategy. MergeMethodResolver resolves a real, available method from an ordered preference list (GithubPrimitives.repositoryMergeCapabilities reads allow_merge_commit/allow_rebase_merge/allow_squash_merge from the repo). Feature branches into develop still prefer squash, falling back to merge or rebase if squash happens to be disabled. Release/hotfix promotions into main never squash — merge or rebase only — since squashing collapses the promoted branch's history that the subsequent back-merge into develop depends on; if a repo only allows squash, this now fails loudly with a clear error instead of silently squashing and corrupting the next back-merge. MergeMethodEntity gains 'rebase' as a third valid value.

    feature/release/hotfix also now install a default PR template into the target repository before opening a PR, if — and only if — that repository doesn't already have one at any of GitHub's recognized template locations. Never overrides an existing template. The bundled default uses GitHub's alert callouts (> [!CAUTION]/[!IMPORTANT]/[!TIP]/[!NOTE]) to color-code Type of Change and Risk by actual severity, a collapsible <details> block for an optional change-flow diagram, and an adversarial-self-review gate ahead of the checklist instead of a habit-checked box list.