v1.4.0

What's New

Features

• Add /deploynope-stale-check command to identify stale branches, aging PRs, and pipeline bottlenecks
• Add 🤓 emoji to Protected by DeployNOPE tag across all commands
• Add release version check rule to prevent version collisions when creating release branches
• Improve production push hook to allow controlled --force-with-lease resets with confirmation

Fixes

• Fix hook bypass vulnerability where commands prefixed with cd or && could slip past interceptors

v1.3.0

What's New

Changelog Configuration & Deployment Integration

• Added 5 new changelog configuration questions to /deploynope-configure:
  • Enable/disable changelog tracking
  • Changelog format (keepachangelog, simple, conventional)
  • Changelog file path
  • Auto-populate from commit history
  • Include GitHub compare links
• Added changelog object to .deploynope.json schema
• Integrated changelog update step into all 3 deployment processes (feature release, hotfix, chore/config)
• Added changelog verification check to /deploynope-postdeploy
• Updated /deploynope-release-manifest positioning table

Style

• Added 🤓 emoji to all Protected by DeployNOPE tags across all commands

From v1.2.0

• Team size and commit message prefix configuration
• Removed development as base branch option to prevent PR target mismatch

v1.2.0

What's New

• Team size configuration — new teamSize setting in /deploynope-configure (stored for future use)
• Commit message prefixes — new commitPrefixes setting; when enabled, DeployNOPE enforces conventional-commit-style prefixes (feat:, fix:, chore:, refactor:, docs:, test:) on all commits
• Base branch guard — removed development as a base branch option to prevent PR target mismatches; prompts to create a release branch when none exists

v1.1.0

v1.1.0 — Framework Visibility, Auto-Activation & Enforcement Hooks

What's new

• "Protected by DeployNOPE" tagging — every response during a DeployNOPE workflow is visibly tagged so the user always knows which framework is active
• Auto-activation via CLAUDE.md — DeployNOPE loads automatically on deployment-related requests (deploy, push, commit, PR, merge, release, branch creation) without needing to invoke a command manually
• Commit confirmation block — mandatory gate showing branch, version, and message before every commit
• Push confirmation block — mandatory gate showing branch, version, and commit list before every push
• Production branch guard — blocks direct pushes to production when staging exists; offers to set up staging infrastructure when it doesn't
• 8 PreToolUse hooks — hard enforcement at the tool level for git commit, push, reset, merge, tag, branch delete, PR create, release create, and branch protection changes
• Correct PR targeting — PRs to production, staging, and development are blocked; only release branches are valid targets

Hooks

All hooks are macOS and Linux compatible (no GNU grep dependency).

v1.0.0

DeployNOPE v1.0.0

First tagged release — deployment safety commands for Claude Code.

Commands

Command	Description
/deploynope-configure	Interactive project setup
/deploynope-deploy	Load the deployment ruleset
/deploynope-preflight	Pre-deployment readiness check — "am I clear to deploy?"
/deploynope-new-work	New branch/task checklist
/deploynope-deploy-status	Deployment progress tracker
/deploynope-release-manifest	Audit trail for production deployments
/deploynope-postdeploy	Post-deployment completion check — "am I actually done?"
/deploynope-rollback	Guided rollback (standard + emergency)
/deploynope-verify-rules	Ruleset self-check

Install

git clone https://github.com/SimTimms/deploynope.git ~/GitHub/deploynope
cd ~/GitHub/deploynope && git checkout v1.0.0
mkdir -p ~/.claude/commands
for f in ~/GitHub/deploynope/.claude/commands/*.md; do
  ln -sf "$f" ~/.claude/commands/"$(basename "$f")"
done