chore(deps): update dependency black to >=24.10.0 #85
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… clean up condition syntax in branch propagation workflow
Alpha Build v0.1.0: Database Schema, Models, Services & Documentation
- Change ruff>=0.15 to ruff>=0.6.0 (0.15 doesn't exist yet) - Replace CPMP_GHCR_TOKEN with GITHUB_TOKEN for GHCR authentication - GITHUB_TOKEN is automatically provided by GitHub Actions with correct permissions
GitHub Actions automatically provides GITHUB_TOKEN with correct permissions for GHCR, so users don't need to create PATs anymore.
- Add @tanstack/react-query, axios, and clsx to frontend dependencies - Remove trailing whitespace from multiple files to pass pre-commit hooks - These were required but missing from package.json
Generated files (coverage/, dist/, .vite/, *.tsbuildinfo) should not be checked by trailing-whitespace or end-of-file-fixer hooks.
This is a Go + React project, not Python. Updated CI workflow to: - Run Go tests (backend) - Run frontend tests with npm (React) - Remove Python test coverage requirement
- Remove duplicate CaddyConfig in proxy_host.go (exists in caddy_config.go) - Remove duplicate HealthHandler in proxy_host_handler.go - Fix version variable names in health_handler.go (SemVer→Version, BuildDate→BuildTime) - Update frontend package-lock.json to sync with package.json dependencies - Backend now compiles successfully (1 test fails but will be fixed later)
- Update docker-compose.yml to use ghcr.io/wikid82/caddyproxymanagerplus:latest - Update docker-compose.dev.yml to use ghcr.io/wikid82/caddyproxymanagerplus:dev - Fix backend test database isolation (remove shared cache mode) - Add testConnection and enabledServers to useRemoteServers hook - Fix frontend test assertions to wait for async state updates - Wrap mutation assertions in waitFor for proper async handling Backend tests: ✅ ALL PASSING (22 tests) Frontend tests:⚠️ 45/49 passing (4 useImport tests need mock refinement)
The backend-builder stage was using golang:latest (Debian) but trying to run Alpine's apk package manager, causing build failures with 'apk: not found'. Changed to golang:alpine for consistency with the RUN commands. Fixes Docker build workflow failures in GitHub Actions.
Added custom Dockerfile validation script that detects mismatches between base image OS (Debian vs Alpine) and package managers (apt vs apk). This will catch errors like: - Using golang:latest (Debian) with apk commands - Using alpine images with apt commands The hook runs automatically on commit and would have caught the recent golang:latest + apk mismatch that caused Docker build failures.
Updated .gitignore, .dockerignore, and .codecov.yml to properly exclude: - Python artifacts (__pycache__, .venv, coverage) - Node artifacts (node_modules, dist, coverage, .vite) - Go artifacts (*.out, coverage files) - Database files (*.db, *.sqlite) - IDE files (.vscode, .idea) - Build artifacts and temporary files - Documentation and scripts from Docker context - Test files from codecov analysis
…m64 build - Wrap async mutations in act() across useImport, useProxyHosts, useRemoteServers tests - Add npm_config_rollup_skip_nodejs_native=1 in Dockerfile to bypass native binary for arm64 - Enable Go module caching in CI via cache-dependency-path on setup-go action - All frontend tests now pass cleanly (49/49) without React Testing Library warnings
- Remove ruff/flake8/pre-commit steps (legacy Python scaffold) - Remove needs dependencies on non-existent lint job - Backend and frontend tests now run independently
- Add Trivy vulnerability scanner after image build - Upload SARIF results to GitHub Security tab - Display critical/high severity issues in workflow logs - Add security-events permission for SARIF upload - Skip scanning on pull requests to save time
- Add format=short to SHA tags to prevent malformed tags - Standardize dev tag naming across workflows (was 'development') - Ensure branch name is properly included in SHA prefix
- Remove type=sha tags that were producing invalid formats like ':-f0d0654' - Keep latest/dev tags for branches and semver tags for releases - SHA is still tracked via image digest and labels
…module; keep Rollup native skipped
… docker-build scan; add outcome gating
…o caddy:2-alpine, upgrade runtime packages
…L/HIGH; pass CADDY_IMAGE build-arg
CI: Add Renovate automation and Caddy v3 monitor
… fail late on CRITICAL/HIGH
chore(deps): pin dependencies
chore(deps): pin dependencies
chore(deps): update actions/add-to-project action to v0.6.1
chore(deps): update dependency alembic to >=1.17.2
chore(deps): update dependency bandit to >=1.9.1
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
Contributor
Author
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update ( If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
>=24.3->>=24.10.0Release Notes
psf/black (black)
v24.10.0Compare Source
Highlights
mypyc-compiled wheels. (#4436) (#4449)
safety issue in Python 3.12.5 that can cause Black's AST safety checks to fail. Please
use Python 3.12.6 or Python 3.12.4 instead. (#4447)
Stable style
X | Ystyle unions.(#4453)
%%magic (#4462)Preview style
def fn(*args: *tuple[*Ts, T]) -> None: pass) (#4440)Caching
--unstable(#4466)Packaging
blackdnow requires a newer version of aiohttp. (#4451)Output
v24.8.0Compare Source
Stable style
# fmt: offis used before a closing parenthesis or bracket. (#4363)Packaging
linked. This improves the PyPI listing for Black. (#4345)
Parser
multiline string (#4339)
(#4401)
\{inside f-strings very well (#4422)(#4423)
Performance
.gitignore(#4415)Blackd
v24.4.2Compare Source
This is a bugfix release to fix two regressions in the new f-string parser introduced in
24.4.1.
Parser
Performance
v24.4.1Compare Source
Highlights
Stable style
Parser
by PEP 696 (#4327)
Integrations
git archiveis skipped (#4313)v24.4.0Compare Source
Stable style
Preview style
ifguards incaseblocks are now wrapped in parentheses when the line is too long.(#4269)
Integrations
use_pyprojectto the GitHub Actionpsf/black. This will read theBlack version from
pyproject.toml. (#4294)Configuration
📅 Schedule: Branch creation - "every weekday" in timezone UTC, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.