Prepare release 3.6.4

[jsoriano]

What does this PR do?

Prepares the release of package-spec 3.6.4.

Changes in this release:

• Enhancement: Add provider_permissions field to package, policy_template, input, and data_stream levels for declaring provider-specific permissions. (#1180)
• Bugfix: Replace profiling data stream type with profiles to align with the OTel Profiles signal name. (#1189) — pending Fleet support, see elastic/ingest-dev#7797.

Release-prep changes also included:

• Point the newest-stack compliance CI rows (9.5.0-SNAPSHOT, 9.4.2-SNAPSHOT) at spec 3.6.4.
• Unskip the "named OTel inputs" compliance scenario (elastic/kibana#271135 backport merged; verified passing on a 9.5.0-SNAPSHOT stack).
• Bump Go to 1.26 (go.mod go 1.26.0, .go-version 1.26.4) to align with elastic-package and integrations.

Why is it important?

Cuts the 3.6.4 patch release so packages can use the new provider_permissions field and the renamed profiles data stream type.

Checklist

• [ ] I have added test packages to test/packages that prove my change is effective.
• I have added an entry in spec/changelog.yml.

Related issues

• Relates Add provider_permissions field for declaring integration permission requirements #1180
• Relates Replace profiling data stream type with profiles #1189
• Relates https://github.com/elastic/ingest-dev/issues/7797

Made with Cursor

Summary by CodeRabbit

• Chores

  • Updated Go version to 1.26.4 and Go toolchain to 1.26.0
  • Bumped specification version to 3.6.4 in compliance tests
  • Finalized changelog for version 3.6.4

• Documentation

  • Updated testing examples and commands to use specification version 3.6.4
  • Added example command for running selected test features

• Bug Fixes

  • Enabled a previously skipped compliance test scenario

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: 506c5b5d-2160-4967-8c87-e00d0db80672

📥 Commits

Reviewing files that changed from the base of the PR and between d2ca364 and 4dfe7b0.

📒 Files selected for processing (6)

• .buildkite/pipeline.trigger.compliance.tests.sh
• .go-version
• AGENTS.md
• compliance/features/basic.feature
• go.mod
• spec/changelog.yml

💤 Files with no reviewable changes (1)

• compliance/features/basic.feature

---

📝 Walkthrough

Walkthrough

This PR releases spec version 3.6.4 by finalizing its changelog entry, removing the @skip annotation from a previously pending compliance scenario, updating the Buildkite CI pipeline and AGENTS.md documentation to reference 3.6.4, and bumping the Go toolchain from 1.25.x to 1.26.x.

Changes

Spec 3.6.4 Release

Layer / File(s)	Summary
Changelog finalization and compliance scenario unskip spec/changelog.yml, compliance/features/basic.feature	version: 3.6.4-next is promoted to version: 3.6.4; pending-issue comments are removed from the 3.6.0 requires entry; @skip is removed from the "Integration package with named OTel inputs can be installed" scenario.
CI pipeline and docs updated to 3.6.4 .buildkite/pipeline.trigger.compliance.tests.sh, AGENTS.md	Buildkite compliance test entries for 9.5.0-SNAPSHOT and 9.4.2-SNAPSHOT move from spec 3.6.3 to 3.6.4; AGENTS.md updates TEST_SPEC_VERSION, format_version, and validator Version examples to 3.6.4 and adds a TEST_SPEC_FEATURES example command.

Go Toolchain Bump

Layer / File(s)	Summary
Go version updated to 1.26.x .go-version, go.mod	.go-version changes from 1.25.9 to 1.26.4; the go directive in go.mod changes from 1.25.0 to 1.26.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

• elastic/package-spec#1168: Activated the same good_integration_otel compliance scenario in compliance/features/basic.feature that this PR unskips.

Suggested reviewers

• mrodm
• teresaromero

Poem

🐇 Hip-hip, three-six-four is here at last!
The skip tag removed, the test runs fast.
The changelog says "next" — no longer true,
Go 1.26 hops in brand new.
The spec is released, the rabbit cheers,
Carrots for all — no more backlog fears! 🥕

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title directly aligns with the main objective of preparing the release of package-spec version 3.6.4, clearly summarizing the primary purpose of the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 4dfe7b0

[teresaromero]

Thanks for reopening the profiles issue, it was closed on merge

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request