release-policy Cursor ruleA
release-policy from v0id-user/setmac is a Cursor rule: instructions the Cursor agent follows in that repo.
mdr add v0id-user/setmac/.cursor/rules/release-policy.mdc@git:20261024.a391928Pins git:20261024.a391928 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Cursor rule
- Repository
- v0id-user/setmac
- Path
.cursor/rules/release-policy.mdc- Versions recorded
- 3
- Latest version
- git:20261024.a391928, committed Oct 24, 2026
- First version recorded
- Mar 18, 2026
- Size
- 1,297 bytes
- Repository stars
- 16
- License
- MIT
Release, versioning, and signing policy for setmac.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Release Policy - Use Conventional Commits and keep one logical change per commit. - Let semantic-release own version bumps. It writes `[tool.setmac].version` in `pyproject.toml` and `__version__` in `cli/src/setmac/__init__.py`; never hand-edit them. The `[project].version` fields stay `0.0.0` because prerelease versions like `1.2.0-canary.1` are not valid PEP 440. - Default to prereleases: push `canary` for `-canary.N`, push `beta` for `-beta.N`. - Every release job runs in the protected `release` environment and waits for the maintainer's approval; release commits and tags are GPG-signed there (`scripts/ci-signing-key.sh`). - Only publish stable when the user explicitly asks. Stable releases run through the manual `Release Stable` workflow from `main`. - Keep release artifacts as `dist/Setmac.dmg` and `cli/dist/setmac-cli`. - Release builds must run through `scripts/release-build.sh`, which signs artifacts and only notarizes when Apple secrets are configured. - If Apple signing secrets are missing, treat builds as ad-hoc signed and include the Gatekeeper workaround in release/install notes: - `xattr -cr /Applications/Setmac.app` …
Read the whole file at its exact version.
How to install
mdr add v0id-user/setmac/.cursor/rules/release-policy.mdc@sha256:c758c670b50ab970The line at the top of this page pins the label git:20261024.a391928, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_qonoqxql5zgauto7)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Mar 18, 2026 and Oct 24, 2026, about one every 110 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261024.a391928 latest | 2026-10-24 | a391928 | 1,297 B | A | view · diff |
| git:20261023.ad13deb | 2026-10-23 | ad13deb | 1,115 B | A | view · diff |
| git:20260318.3137c59 | 2026-03-18 | 3137c59 | 998 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (1297 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
v0id-user/setmac · 16 stars · license MIT · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qonoqxql5zgauto7 GET https://markdownregistry.com/api/v1/resolve?ref=v0id-user/setmac/.cursor/rules/release-policy.mdc GET https://markdownregistry.com/api/v1/blob/c758c670b50ab970999d03c5ee68dc69e3d390886cb506e7cae8700174865cff
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: Cursor rules vs AGENTS.md · which agent file does what.