Skip to content

v1.1.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 15 Jun 18:38
· 8 commits to master since this release
v1.1.1
23fc6c4
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

pbr-cpp-memory-pool v1.1.1 — Maintenance (bug ledger, PR-metadata policy, governance)

A maintenance PATCH. v1.1.1 is purely documentation, process, and tooling — the shipped library is byte-identical to v1.1.0 (no API, ABI, or behaviour change), so every existing consumer is unaffected. It bundles the post-v1.1.0 governance and quality work accumulated on master.

What's in the box

In-repo bug ledger & triage protocol (ADR-0039)

Known defects and the triage of incoming reports now have a durable, reviewable home under docs/bugs/: one Markdown record per defect, BUG-NNNN-<slug>.md under a discovery-date tree docs/bugs/<YYYY>/<MM>/, with a stable monotonic id, structured frontmatter, an index + template, and a lifecycle (open → confirmed → fixed, plus wontfix/duplicate/cannot-reproduce). The ledger is the source of truth (a GitHub issue is referenced, not authoritative). The agent rule (AGENTS.md §7.7) creates a record only for verified, reproducible defects and verifies third-party reports before accepting them (unsubstantiated reports are still recorded as cannot-reproduce/rejected). A new bugs consistency-lint check guards record integrity.

Pull-request metadata policy (ADR-0040)

Every agent-opened PR now also sets a maintainer assignee, exactly one type label (Conventional-Commit type → label; docs reuses the built-in documentation label), and the current open release milestone. The eight type labels and the v1.1.1 milestone were created. Reviewers are deferred (the sole collaborator is the PR author — GitHub forbids self-review) and Projects are deferred (the gh token lacks the project scope); the rule names how each switches on. Codified in AGENTS.md §6.4.

Governance & documentation structure

  • Session journal (ADR-0036) — dated end-of-session checkpoints extracted from ROADMAP.md into docs/journal/ (one file per session under YYYY/MM/), leaving ROADMAP.md a forward plan.
  • New-feature roadmap-placement rule (ADR-0037) — when a feature warrants a new milestone vs. an appended item vs. neither.
  • Per-release changelog split (ADR-0038) — released entries are now one immutable file per release under docs/changelog/v<MAJOR>/, the root CHANGELOG.md keeping only [Unreleased] + the index.
  • SECURITY.md — the public security policy (supported versions, private vulnerability reporting, coordinated disclosure), realizing the addition referenced by the maintenance protocol.

CI & tooling

  • packaging-smoke workflow — end-to-end smoke tests for the vcpkg port and Conan recipe (which cannot be built on the maintainer's box), pinned to the v1.0.0 source tag and run on recipe changes + weekly.
  • GitHub Actions bumped off the deprecated Node 20 runtime onto Node 24.
  • API-reference badge in the README linking to the published Doxygen site.

Architecture Decision Records

Five ADRs accepted since v1.1.0, taking the running total from 35 to 40:

  • ADR-0036 — extract the session journal from ROADMAP.md.
  • ADR-0037 — new-feature roadmap placement (milestone vs. item).
  • ADR-0038 — split the changelog into one file per release.
  • ADR-0039 — in-repo bug ledger and agent triage protocol.
  • ADR-0040 — pull-request metadata policy.

Spec Coverage Map

No change — v1.1.1 is additive documentation/process/tooling, not a spec requirement. All fifteen rows remain ✅ (accepted at v1.0.0, ADR-0029).

What this release does not contain

  • No library code change — the static archive is unchanged from v1.1.0; this is a docs/process/tooling PATCH.
  • The zh-Hans / ja README translations are re-synced to the v1.1.1 status in a follow-up PR (the manifest's two README rows are marked stale in this release).

Verifying the release

Each platform tarball is the same complete cmake --install tree as v1.1.0 (full headers + static archive + CMake package config + pkg-config .pc). SHA-256 checksums are in SHA256SUMS:

sha256sum --check SHA256SUMS

Links

Assets 6
Loading
0 Join discussion