Skip to content

chore(release): backmerge main → develop (v3.0.1)#321

Merged
lerian-studio-midaz-push-bot[bot] merged 11 commits into
developfrom
main
Jul 24, 2026
Merged

chore(release): backmerge main → develop (v3.0.1)#321
lerian-studio-midaz-push-bot[bot] merged 11 commits into
developfrom
main

Conversation

@lerian-studio-midaz-push-bot

Copy link
Copy Markdown

Description

Automated backmerge from main into develop.

A direct merge conflicts with develop. This PR needs review and merge to keep develop in sync.

Created automatically by the backmerge-sync composite action.

Back-merge the 3.0.x hotfix line (CRM regulatory_fields decryption, #320) and
release chores (3.0.1, 3.0.2) into the 3.1.0-beta line so release-candidate
promotes to main without conflicts. Resolutions: go.mod/go.sum kept from
release-candidate (newer, CI-green dependency pair); pkg/engine/CHANGELOG.md
unioned to preserve both stable (1.1.1/1.1.0) and beta (1.1.0-beta.x) entries.

Claude-Session: https://claude.ai/code/session_01WscfYUmQmJ7KWNGE18mXNB
@lerian-studio

lerian-studio commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

🔍 PR Validation Summary

🚫 PR Blocked — 1 blocking failure

Check Status Blocking
Source Branch ✅ success yes
PR Title ❌ failure yes
PR Description ✅ success yes
PR Size ⏭️ skipped no
Auto Labels ⏭️ skipped no
PR Metadata ⏭️ skipped no

Fix the blocking checks above before merge.


🔍 View workflow run

…pare

The dual-module release tags pkg/engine/vX.Y.Z and immediately runs
`go mod download` on that tag. sum.golang.org races on a tag created
seconds ago (publish-then-consume in the same job) and returns 500 while
it fetches the fresh tag from the proxy; the proxy already serves the
content — only checksum-DB verification is flaky. Re-running never helps
because each attempt cuts a newer tag that hits the same race.

Set GONOSUMDB scoped to the engine module on the prepare go commands so
our own just-pushed tag skips sumdb verification (proxy/VCS resolution is
unchanged). Scope is the exact engine module path, so every other
dependency stays checksum-verified.

Claude-Session: https://claude.ai/code/session_01WscfYUmQmJ7KWNGE18mXNB
@lerian-studio

lerian-studio commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

🔴 Lerian Library Version Check — action required

Library Current Latest Status
lib-auth/v2 v2.9.0 v2.9.0 ✅ Current
lib-commons/v5 v5.10.0 v5.10.0 ✅ Current
lib-observability v1.1.0 v2.1.0 🕒 Grace (major bump, expires 2026-07-25)
lib-streaming v1.8.0 v1.9.0 🔴 Needs update
fetcher/pkg/engine v1.2.3 skipped ⏭️ Skipped — ignore file · why?

✅ 2 current · 🔴 1 needs update · 🕒 1 in grace · ⏭️ 1 skipped · ⚠️ 0 unknown

Bump the outdated libraries, or add temporary entries to .lerianstudiolibignore.
🕒 1 major bump(s) are within the grace period. The grace period applies to major bumps only and lasts 3 days — bump them before it expires, or the check will start failing.

@lerian-studio

lerian-studio commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

🔒 Security Scan Results — manager

🚫 PR Blocked — 2 blocking findings

Stage Status Blocking?
Filesystem Scan ✅ Clean
Docker Image Scan ⚠️ 1 finding 🔴 Yes
Docker Hub Health Score ⚠️ 1 finding 🔴 Yes
Pre-release Version Check ✅ Clean

Trivy

Filesystem Scan

✅ No vulnerabilities or secrets found.

Docker Image Scan

Severity Vulnerability Title
CRITICAL/HIGH GHSA-hrxh-6v49-42gf gRPC-Go: xDS RBAC and HTTP/2 Vulnerabilities

Docker Hub Health Score Compliance

⚠️ Policies — 3/4 met

Policy Status
Default non-root user ✅ Passed
No fixable critical/high CVEs ⚠️ Failed
No high-profile vulnerabilities ✅ Passed
No AGPL v3 licenses ✅ Passed

⚠️ Some Docker Hub health score policies are not met. Review the table above.


Pre-release Version Check

✅ No unstable version pins found.


🔍 View full scan logs

@lerian-studio

Copy link
Copy Markdown
Contributor

📊 Unit Test Coverage Report: fetcher-worker

Metric Value
Overall Coverage 87.4% ✅ PASS
Threshold 80%

Coverage by Package

Package Coverage
github.com/LerianStudio/fetcher/v2/components/worker/internal/services 90.0%

Generated by Go PR Analysis workflow

@lerian-studio

Copy link
Copy Markdown
Contributor

📊 Unit Test Coverage Report: fetcher-manager

Metric Value
Overall Coverage 89.7% ✅ PASS
Threshold 80%

Coverage by Package

Package Coverage
github.com/LerianStudio/fetcher/v2/components/manager/cmd/huma-spec 33.4%
github.com/LerianStudio/fetcher/v2/components/manager/internal/adapters/cache 100.0%
github.com/LerianStudio/fetcher/v2/components/manager/internal/adapters/http/in 89.4%
github.com/LerianStudio/fetcher/v2/components/manager/internal/services/command 92.8%
github.com/LerianStudio/fetcher/v2/components/manager/internal/services/query 96.4%

Generated by Go PR Analysis workflow

Changelog atualizado.
@lerian-studio-midaz-push-bot
lerian-studio-midaz-push-bot Bot merged commit b2a39be into develop Jul 24, 2026
17 of 18 checks passed
@lerian-studio

lerian-studio commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

🔒 Security Scan Results — worker

🚫 PR Blocked — 2 blocking findings

Stage Status Blocking?
Filesystem Scan ✅ Clean
Docker Image Scan ⚠️ 1 finding 🔴 Yes
Docker Hub Health Score ⚠️ 1 finding 🔴 Yes
Pre-release Version Check ✅ Clean

Trivy

Filesystem Scan

✅ No vulnerabilities or secrets found.

Docker Image Scan

Severity Vulnerability Title
CRITICAL/HIGH GHSA-hrxh-6v49-42gf gRPC-Go: xDS RBAC and HTTP/2 Vulnerabilities

Docker Hub Health Score Compliance

⚠️ Policies — 3/4 met

Policy Status
Default non-root user ✅ Passed
No fixable critical/high CVEs ⚠️ Failed
No high-profile vulnerabilities ✅ Passed
No AGPL v3 licenses ✅ Passed

⚠️ Some Docker Hub health score policies are not met. Review the table above.


Pre-release Version Check

✅ No unstable version pins found.


🔍 View full scan logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants