chore: release v0.14.0 #201
No reviewers
Labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Slipstream/auto_review!201
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "release/v0.14.0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Prepare release v0.14.0.
CI publishes release-candidate Docker and binary package links on the PR; final release entries are created only after merge to main.
6aefb1fa723d018f0d12This PR prepares for the release of version 0.14.0 by updating the version numbers in the Cargo files and adding a new section to the CHANGELOG. The changes appear straightforward and safe to merge.
3d018f0d126a445c26cfNew commits pushed, approval review dismissed automatically according to repository settings
This release preparation for v0.14.0 includes updates to the changelog, enhancements to the chat command parsing, and the addition of a new
lefthook.ymlfor pre-commit hooks. The changes appear safe to merge, with improvements in handling review corrections and ensuring consistent development environments.Walkthrough
Δ since
3d018f0:lefthook.ymlfile to automate pre-commit checks, ensuring code quality and consistency.lefthookand ensure proper environment setup.6a445c26cf451488e964New commits pushed, approval review dismissed automatically according to repository settings
This release prepares version 0.14.0 with significant changes to the permission system and guardrails, notably blocking direct bash execution and introducing new safety checks for git operations. The changes appear well-structured but require thorough testing to ensure no disruptions in workflows.
Walkthrough
🟡 Warning: Lines 620–759: The change to block all direct bash execution is significant. Ensure that all necessary functionalities are covered by the existing or new typed Pi tools to avoid breaking workflows.
🟡 Warning: The change to deny all bash execution in the permission system is a major shift. Verify that this does not inadvertently block necessary operations or scripts that rely on bash.
451488e9649b6ee2a6c1New commits pushed, approval review dismissed automatically according to repository settings
This PR prepares for the release of version 0.14.0, including changes to environment variable handling and test coverage for non-Unicode values. The changes appear safe to merge, but ensure that all error handling and test cases are adequately covered.
Walkthrough
.pi-lens/and.dependencies/directories.npm:context-mode@1.0.131from the package list.read_env_var_for_ocifor better error handling of environment variables.inner_gateway_process_env_from_lookupto return aResultinstead of anOption.🟡 Warning: Lines 438–448: The change in
inner_gateway_process_env_from_lookupto return aResultinstead of anOptionis significant. Ensure that all callers handle the potential error case appropriately.🟡 Warning: Lines 2186–2196: Ensure that the change to return a
Resultininner_gateway_process_env_from_lookupis correctly handled in all test cases to prevent unexpected panics or test failures.9b6ee2a6c1d50fe43d01New commits pushed, approval review dismissed automatically according to repository settings
This PR prepares for the release of version 0.14.0 by updating the changelog and applying markdown formatting to the threat model document. The changes appear safe to merge, focusing on documentation improvements.
Walkthrough
d50fe43d0148386c77acNew commits pushed, approval review dismissed automatically according to repository settings
This PR prepares the release of version 0.14.0 by updating various project files, including renaming and restructuring directories from
.kiloto.opencode. It also removes several files, ensuring that their functionalities are now covered in the new structure. The changes appear safe to merge, provided that all necessary functionalities are preserved in the new setup.Walkthrough
Directory Restructuring:
.kiloto.opencode, reflecting a change in project organization.File Deletions:
opencodestructure.CHANGELOG Update:
CHANGELOG.md.48386c77acae917b4992New commits pushed, approval review dismissed automatically according to repository settings
The PR updates the release preparation workflow to use structured JSON for PR lookup, improving robustness and maintainability. The changes appear safe to merge, but ensure thorough testing of the new command and jq filter logic.
Walkthrough
tea apitotea pr ls, which uses structured JSON output..head.refto.head.🟡 Warning: The change from
.head.refto.headin the jq filter should be verified to ensure it correctly identifies the branch head in the new structured JSON format. This could affect the logic for identifying existing PRs.ae917b4992a4983ab4c4New commits pushed, approval review dismissed automatically according to repository settings
This release prepares version 0.14.0 with significant updates to the RGR workflow, including the introduction of
rgr_approve_redand stricter requirements for RED evidence. These changes necessitate updates to documentation and workflows to ensure compliance and understanding across the team.Walkthrough
RGR Workflow Changes
rgr_approve_redtool to enforce RED evidence approval before production edits.Validation Enhancements
validateRgrRedEvidenceandassertCleanWorktreeadded to enforce stricter validation of RED evidence and worktree cleanliness.Testing and Documentation
🟡 Warning: The requirement for RED to report exactly one failing test or diagnostic is a significant change. Ensure that all test cases and workflows are updated to handle this constraint.
🟡 Warning: The change to require RED evidence approval before production edits is a critical workflow update. Ensure all team members are aware of this new requirement.
🟡 Warning: The addition of
rgr_approve_redand the requirement for RED approval before production edits is a significant change. Ensure all related processes and documentation are updated accordingly.🟡 Warning: The requirement to record RED approval before production edits is a critical change. Ensure all related processes and documentation are updated accordingly.
🟡 Warning: The requirement for RED evidence to show exactly one failing test or diagnostic is a significant change. Ensure all related processes and documentation are updated accordingly.
🟡 Warning: The requirement for RED evidence to show exactly one failing test or diagnostic is a significant change. Ensure all related processes and documentation are updated accordingly.
🟡 Warning: The requirement for RED evidence to show exactly one failing test or diagnostic is a significant change. Ensure all related processes and documentation are updated accordingly.
🟡 Warning: The requirement for RED evidence to show exactly one failing test or diagnostic is a significant change. Ensure all related processes and documentation are updated accordingly.
a4983ab4c491ac55cebbNew commits pushed, approval review dismissed automatically according to repository settings
This release prepares for version 0.14.0, introducing significant changes to the architecture documentation and ADR workflow. The updates include new ADRs, the restructuring of existing documentation, and enhancements to the ADR tooling. The changes appear safe to merge, with no critical issues identified.
Walkthrough
Δ since
a4983ab:Documentation and ADRs:
docs/ARCHITECTURE.mdand the consolidation of ADRs into a more centralized format suggest a move towards a more streamlined documentation process.Tooling and Tests:
auto-review-discipline.tsplugin, enhancing the workflow for creating, updating, and managing ADRs.Threat Model and Security:
91ac55cebb90dd0ffdccNew commits pushed, approval review dismissed automatically according to repository settings
This PR prepares for the release of version 0.14.0 by updating the changelog and adding documentation for a new ADR that changes the CI and distribution strategy. The changes appear safe to merge, but ensure that all team members are informed of the new ADR and its implications.
Walkthrough
Δ since
91ac55c:CHANGELOG.md:
docs/ADR-0018-just-based-checks-and-binary-first-distribution.md:
docs/ARCHITECTURE.md:
🟡 Warning: Lines 1–42: The new ADR-0018 document introduces significant changes to the project's CI and distribution strategy. Ensure that all team members are aware of these changes and that any necessary updates to internal processes or documentation are made.
🟡 Warning: Lines 25–45: The architecture document now reflects a shift away from Docker/OCI images as the primary distribution artifact. Verify that all deployment scripts and documentation are updated to align with this new strategy.
90dd0ffdcc8dfdd362dfNew commits pushed, approval review dismissed automatically according to repository settings
This PR prepares for the v0.14.0 release by updating workflows and documentation, and removing several release tooling tests. The changes appear to streamline the release process, but ensure that all necessary tests and checks are still covered.
Walkthrough
Δ since
90dd0ff:Workflow Changes:
.forgejo/workflows/release-publish.yml: Removed the patterntests/release_tooling/*.shfrom the token-bearing publish refusal list, which may affect how changes to these tests are handled.Documentation Updates:
CHANGELOG.md: Added an entry for retiring release workflow text tests.docs/THREAT-MODEL.md: Updated to reflect changes in allowed files for release PRs, removingtests/release_tooling/*.sh.Build Configuration:
flake.nix: Removed therelease-toolingbuild, indicating a shift in how release tooling is managed.Test Removals:
tests/release_tooling/, suggesting a change in testing strategy for release tooling.🟡 Warning: The removal of the
tests/release_tooling/*.shpattern from the release-publish workflow may unintentionally allow changes to these test files without triggering a refusal for token-bearing publish. Ensure this change is intentional and that the tests are no longer relevant for the release process.🟡 Warning: The removal of the allowance for
tests/release_tooling/*.shin the threat model suggests a change in how release tooling tests are handled. Ensure that this aligns with the new release process and that any necessary tests are covered elsewhere.🟡 Warning: The removal of the
release-toolingbuild inflake.nixindicates a significant change in how release tooling is managed. Ensure that all necessary functionality is covered by other parts of the build process.8dfdd362df34855f28a5New commits pushed, approval review dismissed automatically according to repository settings
34855f28a566741355b1This PR prepares for the release of version 0.14.0 by updating the version numbers in the Cargo files and adding the release notes to the CHANGELOG. The changes appear straightforward and safe to merge.
66741355b11db013a832New commits pushed, approval review dismissed automatically according to repository settings
This PR updates the CI workflows to stop publishing PR packages and modifies the release preparation and publication processes. The changes appear safe to merge, but ensure alignment with the project's release strategy.
Walkthrough
Δ since
6674135:CI Workflow Changes
.forgejo/workflows/ci.ymlpr-packagesjob, which previously handled the publication of PR artifact packages.pr-publication-artifactsdirectory and related steps..forgejo/workflows/release-prepare.yml.forgejo/workflows/release-publish.ymljqandcurlin the release publication process.CHANGELOG.md
🟡 Warning: The removal of the
pr-packagesjob and associated steps significantly changes the CI workflow by stopping the publication of PR packages. Ensure that this change aligns with the project's release strategy and that any necessary documentation is updated to reflect this change.🟡 Warning: The removal of
jqandcurlfrom the Nix profile installation in therelease-publish.ymlworkflow may affect any steps that rely on these tools. Verify that these tools are no longer needed or are provided by other means.