Skip to content

Bump the linked Go profiler to v0.7.0 - #6

Merged
colinjlacy merged 3 commits into
runtimeconditions:mainfrom
itvi-1234:bump-go-profiler-0.7.0
Nov 13, 2026
Merged

colinjlacy merged 3 commits into
runtimeconditions:mainfrom
itvi-1234:bump-go-profiler-0.7.0

Conversation

@itvi-1234

Copy link
Copy Markdown
Member

go-rc-profiler v0.7.0 writes profile extensions as : and resolves extension dependencies that carry no version annotation.

go.mod and the component lock move to v0.7.0. The lock carries the release commit and the archive and executable SHA-256 of each platform build. The archive hashes match the release checksums, and the same extraction method reproduces the v0.6.1 hashes already in the lock. The smoke test now expects the short form for the common-integrations extension.

go-rc-profiler v0.7.0 writes profile extensions as <short-url>:<version> and
resolves extension dependencies that carry no version annotation.

go.mod and the component lock move to v0.7.0. The lock carries the release
commit and the archive and executable SHA-256 of each platform build. The
archive hashes match the release checksums, and the same extraction method
reproduces the v0.6.1 hashes already in the lock. The smoke test now expects
the short form for the common-integrations extension.
The fixture declared only a common-integrations cache, so the smoke test
checked one extension. It now also uses an env-configuration binding, which
depends on common-integrations by id alone. The test expects both extensions
in the short <url>:<version> form and validates the env binding package as
well.
The fixture id was https://bindings.example.test/parity:0.1.0, with the version
inside the id, so the profile now lists it as the id plus :0.1.0. A canonical id
ending in /0.1.0/runtimeconditions.extension.yaml gives the short form
https://bindings.example.test/parity:0.1.0, which is what the smoke test now
expects.
@colinjlacy
colinjlacy merged commit e3b8bd1 into runtimeconditions:main Nov 13, 2026
4 checks passed
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.

2 participants