Integrate master for portalocker v4.0.0 - #132
Conversation
Bumps the actions group with 1 update: [coactions/dynamic-matrix](https://github.com/coactions/dynamic-matrix). Updates `coactions/dynamic-matrix` from 3 to 4 - [Release notes](https://github.com/coactions/dynamic-matrix/releases) - [Commits](coactions/dynamic-matrix@v3...v4) --- updated-dependencies: - dependency-name: coactions/dynamic-matrix dependency-version: '4' dependency-type: direct:production update-type: version-update:semver-major dependency-group: actions ... Signed-off-by: dependabot[bot] <support@github.com>
…ctions-2a50a5be6e
Bumps the actions group with 1 update: [actions/checkout](https://github.com/actions/checkout). Updates `actions/checkout` from 4 to 5 - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v4...v5) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '5' dependency-type: direct:production update-type: version-update:semver-major dependency-group: actions ... Signed-off-by: dependabot[bot] <support@github.com>
…ctions-a331d3ec2d
Bumps the actions group with 2 updates: [scientific-python/repo-review](https://github.com/scientific-python/repo-review) and [actions/stale](https://github.com/actions/stale). Updates `scientific-python/repo-review` from 0.12.2 to 0.12.3 - [Release notes](https://github.com/scientific-python/repo-review/releases) - [Changelog](https://github.com/scientific-python/repo-review/blob/main/docs/changelog.md) - [Commits](scientific-python/repo-review@v0.12.2...v0.12.3) Updates `actions/stale` from 9 to 10 - [Release notes](https://github.com/actions/stale/releases) - [Changelog](https://github.com/actions/stale/blob/main/CHANGELOG.md) - [Commits](actions/stale@v9...v10) --- updated-dependencies: - dependency-name: scientific-python/repo-review dependency-version: 0.12.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: actions - dependency-name: actions/stale dependency-version: '10' dependency-type: direct:production update-type: version-update:semver-major dependency-group: actions ... Signed-off-by: dependabot[bot] <support@github.com>
…ctions-dbca84b406
Bumps the actions group with 1 update: [actions/upload-artifact](https://github.com/actions/upload-artifact). Updates `actions/upload-artifact` from 4 to 5 - [Release notes](https://github.com/actions/upload-artifact/releases) - [Commits](actions/upload-artifact@v4...v5) --- updated-dependencies: - dependency-name: actions/upload-artifact dependency-version: '5' dependency-type: direct:production update-type: version-update:semver-major dependency-group: actions ... Signed-off-by: dependabot[bot] <support@github.com>
…ctions-dc500464ed Bump actions/upload-artifact from 4 to 5 in the actions group
coactions/dynamic-matrix fails on current runner images because its pinned cffi cannot compile under the bundled Python, so matrix generation (and with it every test job) has been failing. The matrix it used to derive is now spelled out statically; runner labels updated to currently supported images.
The repo-review action installs its rule plugins unpinned, so new pre-commit and pytest style rules started failing this frozen branch without any repository change. The affected rules concern tooling that the 4.0.0 modernization replaces wholesale.
The lint workflow installs ruff unpinned, and 0.16 added RUF036 which rejects unions with None in the middle.
Restore CI on master: static test matrix, floating-linter compatibility
The image's default Python on PATH is 32-bit, so uv resolved every tox environment as win32 where cryptography (pulled in through types-redis) ships no wheel and fails its Rust source build for lack of OpenSSL. Managed uv interpreters are always x64 and independent of the image.
The pyXX environments invoke pyright as an allowlisted external, which only works where CI installs it globally. AppVeyor does not, so the type-check step failed with a missing executable.
Unpinned pyright floats ahead of the uv.lock version that the GitHub jobs use and newer releases add deprecation diagnostics that this frozen branch does not chase.
Fix the AppVeyor build: 64-bit interpreters, env-local pinned pyright
Bumps the actions group with 4 updates in the / directory: [actions/checkout](https://github.com/actions/checkout), [supercharge/redis-github-action](https://github.com/supercharge/redis-github-action), [actions/upload-artifact](https://github.com/actions/upload-artifact) and [actions/stale](https://github.com/actions/stale). Updates `actions/checkout` from 5 to 7 - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v5...v7) Updates `supercharge/redis-github-action` from 1.8.0 to 1.8.1 - [Release notes](https://github.com/supercharge/redis-github-action/releases) - [Changelog](https://github.com/supercharge/redis-github-action/blob/main/CHANGELOG.md) - [Commits](supercharge/redis-github-action@1.8.0...1.8.1) Updates `actions/upload-artifact` from 5 to 7 - [Release notes](https://github.com/actions/upload-artifact/releases) - [Commits](actions/upload-artifact@v5...v7) Updates `actions/stale` from 10 to 11 - [Release notes](https://github.com/actions/stale/releases) - [Changelog](https://github.com/actions/stale/blob/main/CHANGELOG.md) - [Commits](actions/stale@v10...v11) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major dependency-group: actions - dependency-name: actions/stale dependency-version: '11' dependency-type: direct:production update-type: version-update:semver-major dependency-group: actions - dependency-name: actions/upload-artifact dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major dependency-group: actions - dependency-name: supercharge/redis-github-action dependency-version: 1.8.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: actions ... Signed-off-by: dependabot[bot] <support@github.com>
…ctions-4e338df84e Bump the actions group across 1 directory with 4 updates
There was a problem hiding this comment.
Pull request overview
This PR integrates the current master line into the develop track for the upcoming portalocker v4.0.0 release, and documents a detailed release design + step-by-step execution/verification plan, while updating the stale-issue workflow action version.
Changes:
- Added a v4.0.0 release design spec documenting integration strategy, release execution, and failure handling.
- Added a detailed implementation plan for performing the integration merge, running local gates, publishing via the signed release helper, and verifying GitHub/PyPI state.
- Updated the
actions/staleworkflow to useactions/stale@v11.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| docs/superpowers/specs/2026-08-01-portalocker-4.0.0-release-design.md | Adds the high-level release design and constraints for publishing v4.0.0 from develop. |
| docs/superpowers/plans/2026-08-01-portalocker-4.0.0-release.md | Adds the detailed operational runbook for integrating master, publishing v4.0.0, and verifying outcomes. |
| .github/workflows/stale.yml | Bumps the stale-management action version for issue hygiene automation. |
Suppressed comments (1)
docs/superpowers/plans/2026-08-01-portalocker-4.0.0-release.md:278
- This step invokes the release helper via a user-specific absolute path. Use the command name (from PATH) or a variable so the plan works across machines.
/Users/rick/bin/build_and_upload_release "$release_message"
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 42a0d85850
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Summary
Verification
uv run pytestuv run tox -e ruff,mypy,basedpyright,pyrefly,ty,codespell,repo-review,docsuv run pyrightuv buildandtwine check