Files

T

vasilito cb424d7448 build: static patch-sanity linter (shift-left the malformed-patch class)

verify-patch-sanity.py validates every active recipe .patch has internally-
consistent hunk line counts — catching the 'malformed patch at line N' failure
at commit/CI/preflight time instead of hours into a cook. This cycle hit that
class three times (qtwaylandscanner, sddm, xwayland), each only discovered when
cookbook tried to apply the patch.

Running it across the repo found 29 latent malformed patches (validated against
GNU patch: e.g. relibc/P3-sysv-ipc reproduces 'malformed patch at line 22').
They were harmless only because they sit in vendored recipes (baked, not re-
applied) — but would fail on any version-bump re-derivation. --fix recounts the
hunk headers (body untouched) and repaired all 29.

Wired into build-preflight.sh (Phase 1.0D) and redbear-ci.yml, with a unit test
(test-patch-sanity.sh). Skips archived/legacy trees and unvalidatable formats
(empty placeholders, bare-@@ git hunks).

2026-08-01 05:13:02 +03:00

1.3 KiB

Raw Blame History

How to release

Make sure you're on main and synced to HEAD
Ensure the project builds and tests run
- parallel -j0 exec ::: test/*_test can help ensure everything at least passes
Prepare release notes
- git log $(git describe --abbrev=0 --tags)..HEAD gives you the list of commits between the last annotated tag and HEAD
- Pick the most interesting.
Create one last commit that updates the version saved in CMakeLists.txt and MODULE.bazel to the release version you're creating. (This version will be used if benchmark is installed from the archive you'll be creating in the next step.)

project (benchmark VERSION 1.8.0 LANGUAGES CXX)

module(name = "com_github_google_benchmark", version="1.8.0")

Create a release through github's interface
- Note this will create a lightweight tag.
- Update this to an annotated tag:
  - git pull --tags
  - git tag -a -f <tag> <tag>
  - git push --force --tags origin
Confirm that the "Build and upload Python wheels" action runs to completion
- Run it manually if it hasn't run.
- IMPORTANT: When re-running manually, make sure to select the newly created <tag> as the workflow version in the "Run workflow" tab on the GitHub Actions page.

1.3 KiB Raw Blame History

How to release

1.3 KiB

Raw Blame History