Propagate Development into Beta-Release#1016
Merged
Merged
Conversation
… session management
…nd add golangci-lint tracking
…e and orthrus components
…revent log injection Co-authored-by: Copilot <copilot@github.com>
Weekly: Promote nightly to main (2026-04-27)
fix(deps): update non-major-updates
Propagate changes from main into development
…revent log injection Co-authored-by: Copilot <copilot@github.com>
…ovider test failures
chore(deps): update non-major-updates
…e, delete, and status retrieval
…, provision, get, delete, and revoke operations
fix(deps): update non-major-updates
… and node-releases versions
… @csstools/css-syntax-patches-for-csstree to latest versions
…etter organization
…ccessListForm, AccessListSelector, and CSPBuilder components
Frontend ESLint was blocked by three root causes: duplicate TypeScript devDependency declarations in package.json, a react-refresh violation from utility functions co-located with components in CertificateList, and five form label associations on non-labelable elements. Two disabled tests using .skip() were also replaced with .todo() as required by the vitest/prefer-todo rule. Backend tests were failing due to two independent root causes. First, parallel execution of the security handler test suite caused SQLITE_BUSY errors because background audit goroutines were not being cleaned up between tests. This was resolved by adding an exported Close() method to SecurityHandler and registering cleanup at all 14 call sites, combined with switching the audit test database from a file-based WAL SQLite to an in-memory instance. Second, the Cloudflare provider TestStart_CapturesStdoutOutput test had a race condition where the ring buffer was closed before scanner goroutines could write output; this was fixed using a sync.WaitGroup to gate buffer closure on scanner completion. All CI jobs now pass locally: 0 ESLint errors, 0 TypeScript errors, 481 frontend tests at 89.3% coverage, 7395 backend tests at 88.5% coverage, and 5/5 race-detector passes on the Cloudflare provider.
fix(deps): update non-major-updates
fix(deps): update non-major-updates
Contributor
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
…rors The frontend builder stage failed in CI with ECONNRESET when fetching the npm package from registry.npmjs.org. The apk upgrade completed successfully; only the npm self-upgrade network call was affected. Added --fetch-retries=5 and --fetch-retry-mintimeout=10000 to the npm install -g command so transient registry connection resets are retried automatically before the build aborts, eliminating the need for manual CI re-runs on flaky network conditions.
Contributor
✅ Supply Chain Verification Results✅ PASSED 📦 SBOM Summary
🔍 Vulnerability Scan
📎 Artifacts
Generated by Supply Chain Verification workflow • View Details |
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.