Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions .github/rulesets/tags.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
{
"name": "release-tags",
"target": "tag",
"enforcement": "active",
"conditions": {
"ref_name": {
"include": ["refs/tags/v*.*.*"],
"exclude": []
}
},
"rules": [
{ "type": "deletion" },
{ "type": "non_fast_forward" },
{ "type": "update" }
],
"bypass_actors": [
{ "actor_id": 5, "actor_type": "RepositoryRole", "bypass_mode": "always" }
]
}
15 changes: 15 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,21 @@

## [Unreleased]

## [0.5.5] - 2026-05-12

### Added

- Tag protection ruleset (`release-tags`) on the repository. Any tag matching `refs/tags/v*.*.*` now blocks deletion, force-push (`non_fast_forward`), and tag-update operations, so a published release tag cannot be silently rewritten to point at a different commit. Configured via the GitHub API; the canonical definition lives at `.github/rulesets/tags.json` for review and re-apply (`.github/rulesets/tags.json`)
- README now displays two additional badges alongside the existing CI / Codecov / CodeQL set: a Libraries.io dependency status badge for `@hiprax/errors` and an npm-provenance badge linking to npm's provenance docs (the release workflow already publishes with `--provenance`) (`README.md`)

### Changed

- Repository settings: `delete_branch_on_merge` and `allow_update_branch` are now enabled at the repo level. Merged PR branches are auto-deleted from the remote, and contributors can update a PR branch from the GitHub UI without dropping to the CLI when `main` has moved ahead

### Docs

- `CLAUDE.md` "CI / Workflow Conventions" section now documents the tag-protection ruleset alongside the existing branch-protection guidance, so a future contributor can re-create the ruleset from the checked-in `.github/rulesets/tags.json` without reverse-engineering the GitHub UI (`CLAUDE.md`)

## [0.5.4] - 2026-05-12

### Removed
Expand Down
2 changes: 2 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,8 @@
[![CI](https://github.com/Hiprax/errors/actions/workflows/ci.yml/badge.svg)](https://github.com/Hiprax/errors/actions/workflows/ci.yml)
[![codecov](https://codecov.io/gh/Hiprax/errors/branch/main/graph/badge.svg)](https://codecov.io/gh/Hiprax/errors)
[![CodeQL](https://github.com/Hiprax/errors/actions/workflows/codeql.yml/badge.svg)](https://github.com/Hiprax/errors/actions/workflows/codeql.yml)
[![Dependencies](https://img.shields.io/librariesio/release/npm/@hiprax/errors)](https://libraries.io/npm/@hiprax%2Ferrors)
[![npm provenance](https://img.shields.io/badge/npm-provenance-blue?logo=npm&logoColor=white)](https://docs.npmjs.com/generating-provenance-statements)

A small, typed error toolkit for Express.js apps. Zero runtime dependencies.

Expand Down
4 changes: 2 additions & 2 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@hiprax/errors",
"version": "0.5.4",
"version": "0.5.5",
"description": "A modular error handling solution for Express.js applications.",
"main": "./dist/index.js",
"module": "./dist/index.mjs",
Expand Down