Prepare release 3.6.1#1145
Conversation
Made-with: Cursor
Made-with: Cursor
Made-with: Cursor
Made-with: Cursor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
💤 Files with no reviewable changes (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughThis pull request updates several versions and test configurations and re-enables tests. The Go toolchain is bumped from 1.25.8 to 1.25.9. A Buildkite compliance test invocation changes a spec from 3.6.0 to 3.6.1, and documentation examples in AGENTS.md and semantic validator registration are updated to 3.6.1. The changelog entry key is changed from 🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
|
||
| # Generate each test we want to do. | ||
| compliance_test 9.4.0-SNAPSHOT 3.6.0 | ||
| compliance_test 9.4.0-SNAPSHOT 3.6.1 |
There was a problem hiding this comment.
I would keep this compliance test for now as 9.4.0-SNAPSHOT.
Related PR: elastic/kibana#261362.
Even this spec max could be used for 9.5.0-SNAPSHOT, I think I would keep it for now with 9.4.0-SNAPSHOT this compliance test.
…gling enhancements
…ynamic signal types in dataset.feature
💚 Build Succeeded
History
|
What does this PR do?
Prepares the 3.6.1 package-spec release: finalizes
spec/changelog.yml, points latest-stack compliance CI at spec 3.6.1, refreshes the Go patch in.go-version, and updatesAGENTS.mdexamples to match.Follow-up commits on this branch also:
sections/ per-varsection, andshow_divideron inputs).@skipfrom the OTeldynamic_signal_typesdataset compliance scenarios incompliance/features/dataset.featureso those scenarios run again.Why is it important?
Ships accumulated spec changes as 3.6.1 so integrators can depend on the released semver and CI validates the stack against that version. Re-enabling the dataset scenarios keeps compliance coverage aligned with current routing behavior for dynamic signal types.
Release contents (from
spec/changelog.ymlfor 3.6.1)use_apm,data_stream.dataset) to enforce correct types and constraints when explicitly overridden in package manifests. (PR #1134)settings.num_failure_retriesoption. (Issue #1124)geo_shapeas a valid field type for integrations. (PR #1132)_dev/build/docsfolder in content packages to support README auto-generation. (PR #1144)sectionslist for defining named section headers, andsectionattribute on vars for assigning variables to a section in the Fleet UI. (PR #1133)show_divideroptional boolean to input objects to suppress horizontal dividers in the Fleet UI. (PR #1133)Go toolchain
Repository
godirective remains 1.25.0;.go-versionupdated to 1.25.9 (latest 1.25 patch per go.dev). Go 1.26.x is now the latest stable minor; this PR does not bumpgo.modminor. Ifelastic/elastic-packageandelastic/integrationsdefault branches move to 1.26, we can follow with a separate minor bump PR.Checklist
I have added test packages totest/packagesthat prove my change is effective.I have added an entry inspec/changelog.yml.Related issues
Made with Cursor