zqr10159 opened a new pull request, #4444:
URL: https://github.com/apache/hertzbeat/pull/4444

   ## What's changed?
   
   Propose moving the `2.0.0` development line into `master` for continued 
community development. This draft is a mainline migration review, not a stable 
2.0 release announcement or authorization to merge or publish.
   
   The branch includes the entity-centered metrics, logs and traces query paths 
in `hertzbeat-observability` and their warehouse/Greptime integrations, shared 
investigation context, and the Vite React `web-app` with entity, topology, 
instrumentation and Explore workflows. The scope and limitations are documented 
in [the alpha 
preview](https://github.com/apache/hertzbeat/blob/0514e50d4c2355ac0970af851926db9c6162e9ed/docs/alpha-preview.md)
 and [query-context 
contract](https://github.com/apache/hertzbeat/blob/0514e50d4c2355ac0970af851926db9c6162e9ed/docs/observability-query-context-v1.md).
 These implementations do not establish full product parity or production 
acceptance for every workflow.
   
   [CI repair commit 
0514e50](https://github.com/apache/hertzbeat/commit/0514e50d4c2355ac0970af851926db9c6162e9ed)
 restores the managed OTel runtime inputs still consumed by the Java supervisor 
and Collector release profiles. It selects Go 1.26.9 and compatible patched 
transport/OTel SDK dependencies while retaining the Collector 0.156.0 
components and vulnerability, license, reproducibility and release-content 
gates. It also removes duplicate Backend CI concurrency, repairs the Maven 
release-command layout check, and replaces the organization-denied Markdown 
action with its pinned CLI version.
   
   ## Validation and outstanding checks
   
   Completed locally for the CI repair:
   
   - Runtime configuration validation, five-platform Go cross-builds, 
license/release-asset gates, SBOM/inventory/checksum checks, and repeated-build 
reproducibility passed.
   - `govulncheck` found zero called-symbol or imported-package 
vulnerabilities. A module-only `GO-2026-5932` OpenPGP advisory remains in 
`golang.org/x/[email protected]`; the affected OpenPGP package is not imported. No 
suppression was added.
   - 51 focused Python tests passed; Markdown CLI 0.18.1 checked 2,271 files 
with zero errors and valid/invalid fixtures confirmed exit 0/1.
   - Targeted duplicate-key, shell syntax, layout and whitespace checks passed. 
Actionlint still reports the existing setup-python@v4 runtime warning and its 
outdated macos-15-intel label table. The Markdown CLI pins its top-level 
version but has no lockfile for transitive dependencies.
   
   Remote push checks at draft preparation: [Backend 
CI](https://github.com/apache/hertzbeat/actions/runs/37939501756) is queued; 
[DOC CI](https://github.com/apache/hertzbeat/actions/runs/37939501903) is in 
progress. Neither is being reported as green. PR checks, including the default 
Hybrid Collector gate, remain pending verification; no manual release workflow 
is requested.
   
   These focused results do not establish whole-branch acceptance. Full JVM 
Collector packaging, native/GraalVM packaging, container validation, live 
end-to-end telemetry/supervisor behavior, and actual Linux/Windows execution 
have not been completed in this repair pass. Cross-compilation on macOS is not 
cross-system runtime validation.
   
   ## Mainline migration decisions before merge
   
   - [ ] Preserve an agreed current 1.x maintenance point/branch and define its 
maintenance policy before advancing master.
   - [ ] Decide how to retain the 2.0 development history. The current 
`.asf.yaml` enables squash only; merge/rebase are disabled. This draft changes 
no merge policy.
   - [ ] Agree the documentation/asf-site rollout and default-branch Nightly 
image publication plan before merging. The PR event itself does not publish 
either; advancing master can affect both.
   - [ ] Review the required PR checks and remaining alpha, upgrade and 
release-acceptance limits before making this draft ready for merge.
   
   ## Checklist
   
   - [ ] I have read the linked Contributing Guide.
   - [x] Relevant runtime documentation and CI regression tests are included.
   - [ ] All necessary whole-branch unit, integration and e2e cases have passed.
   
   ## Add or update API
   
   - [ ] The necessary e2e tests for the branch's API changes have passed.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to