RedBear-OS

vasilito/RedBear-OS

Fork 0

Commit Graph

Author	SHA1	Message	Date
vasilito	99e5641127	feat: release-bump pipeline + external graphics version sync Pipeline (3 operator asks): - bump-release.sh: canonical orchestrator (forks + sources + external) - upgrade-forks.sh --to=<tag>: rebase forks with diverged-mode guard - bump-graphics-recipes.sh: map-driven group-aware graphics bumps - check-external-versions.sh: drift checker for Qt6/KF6/Plasma/Mesa/Wayland - refresh-fork-upstream-map.sh: append-only map updater with --check - post-checkout-version-sync.sh + install-git-hooks.sh: opt-in branch hook - external_version_lib.py: shared version-parsing/bumping library - external-upstream-map.toml: ~80 external package entries - bump-fork.sh: deprecated (REDBEAR_I_KNOW_BUMP_FORK_IS_DEPRECATED=1) - RELEASE-BUMP-WORKFLOW.md: operator runbook Quality fixes (8 defects from two independent audits): - blake2b stable cache keys (was hash(), non-portable) - atomic cache writes via os.replace - version_sort_key pre-release demotion (was sorting after finals) - apply_ver_transform re.error tolerance - grep \|\| true (pipefail abort) - cd failure detection in upgrade-forks - sed URL escape (injection hardening) - refresh-fork-upstream-map last-row drop fix Doc cleanup: - Archive 5 obsolete plans to local/docs/archived/ - Remove 14 stale/superseded docs - Update 18 docs to reference bump-release.sh and fix inbound links - TOOLS.md drift fixes	2026-07-18 14:45:41 +09:00
vasilito	4a37ae1a57	phase 1.2: move 137 legacy .patch symlinks out of path-source recipes Per AGENTS.md § 'Local Fork Recipe Directories Must Not Carry Patch Files', the symlinks under recipes/core/{base,kernel,relibc, bootloader,installer}/ pointing at the canonical local/patches/<comp>/ patches were violations. The recipes use path = '...' source so the cookbook would never apply these patches; the symlinks were a navigation aid only. This commit moves all 137 valid symlinks (and the redox.patch counterparts) to local/docs/legacy-recipe-patches/<comp>/ with a README explaining the rationale and pointing readers at the canonical patch location. The patches themselves (local/patches/<comp>/*.patch) are NOT modified — they remain git-tracked at their canonical location. Per AGENTS.md 'NEVER DELETE' policy the patches stay in their canonical home; only the navigation aid symlinks are relocated. Breakdown: base (61) - legacy-recipe-patches/base/ kernel (26) - legacy-recipe-patches/kernel/ relibc (46) - legacy-recipe-patches/relibc/ bootloader (3) - legacy-recipe-patches/bootloader/ installer (1) - legacy-recipe-patches/installer/ After this commit, recipes/core/<comp>/.patch references all show zero matches per AGENTS.md rule.	2026-07-12 01:35:58 +03:00

Author

SHA1

Message

Date

vasilito

99e5641127

feat: release-bump pipeline + external graphics version sync

Pipeline (3 operator asks):
- bump-release.sh: canonical orchestrator (forks + sources + external)
- upgrade-forks.sh --to=<tag>: rebase forks with diverged-mode guard
- bump-graphics-recipes.sh: map-driven group-aware graphics bumps
- check-external-versions.sh: drift checker for Qt6/KF6/Plasma/Mesa/Wayland
- refresh-fork-upstream-map.sh: append-only map updater with --check
- post-checkout-version-sync.sh + install-git-hooks.sh: opt-in branch hook
- external_version_lib.py: shared version-parsing/bumping library
- external-upstream-map.toml: ~80 external package entries
- bump-fork.sh: deprecated (REDBEAR_I_KNOW_BUMP_FORK_IS_DEPRECATED=1)
- RELEASE-BUMP-WORKFLOW.md: operator runbook

Quality fixes (8 defects from two independent audits):
- blake2b stable cache keys (was hash(), non-portable)
- atomic cache writes via os.replace
- version_sort_key pre-release demotion (was sorting after finals)
- apply_ver_transform re.error tolerance
- grep || true (pipefail abort)
- cd failure detection in upgrade-forks
- sed URL escape (injection hardening)
- refresh-fork-upstream-map last-row drop fix

Doc cleanup:
- Archive 5 obsolete plans to local/docs/archived/
- Remove 14 stale/superseded docs
- Update 18 docs to reference bump-release.sh and fix inbound links
- TOOLS.md drift fixes

2026-07-18 14:45:41 +09:00

vasilito

4a37ae1a57

phase 1.2: move 137 legacy .patch symlinks out of path-source recipes

Per AGENTS.md § 'Local Fork Recipe Directories Must Not Carry Patch
Files', the symlinks under recipes/core/{base,kernel,relibc,
bootloader,installer}/ pointing at the canonical local/patches/<comp>/
patches were violations. The recipes use path = '...' source so the
cookbook would never apply these patches; the symlinks were a
navigation aid only.

This commit moves all 137 valid symlinks (and the redox.patch
counterparts) to local/docs/legacy-recipe-patches/<comp>/ with a
README explaining the rationale and pointing readers at the canonical
patch location.

The patches themselves (local/patches/<comp>/*.patch) are NOT
modified — they remain git-tracked at their canonical location.
Per AGENTS.md 'NEVER DELETE' policy the patches stay in their
canonical home; only the navigation aid symlinks are relocated.

Breakdown:
  base (61)         - legacy-recipe-patches/base/
  kernel (26)       - legacy-recipe-patches/kernel/
  relibc (46)       - legacy-recipe-patches/relibc/
  bootloader (3)    - legacy-recipe-patches/bootloader/
  installer (1)     - legacy-recipe-patches/installer/

After this commit, recipes/core/<comp>/.patch references all show
zero matches per AGENTS.md rule.

2026-07-12 01:35:58 +03:00

2 Commits