Skip to content

Fix v1alpha2 follow ups - #39

Merged
colinjlacy merged 5 commits into
runtimeconditions:mainfrom
itvi-1234:fix-v1alpha2-follow-ups
Nov 14, 2026
Merged

colinjlacy merged 5 commits into
runtimeconditions:mainfrom
itvi-1234:fix-v1alpha2-follow-ups

Conversation

@itvi-1234

Copy link
Copy Markdown
Member
  • Add the generated NATS service 0.2.0 extension release that the semantic bridge already describes, and a test that it matches the compiler output.
  • Point the nats-service rootExtension at 0.2.0.
  • Bump the common-integrations and env-configuration Go and TypeScript bindings to 0.3.0. Their 0.2.0 versions are already published from v1alpha1, and v1alpha2 would otherwise reuse the same version with different content.
  • Drop the stale NATS dependency sentence from the env-configuration README; the definition only depends on common-integrations v1alpha2.

- Add the generated NATS service 0.2.0 extension release that the semantic bridge
  already describes, and a test that it matches the compiler output.
- Point the nats-service rootExtension at 0.2.0.
- Bump the common-integrations and env-configuration Go and TypeScript bindings to
  0.3.0. Their 0.2.0 versions are already published from v1alpha1, and v1alpha2
  would otherwise reuse the same version with different content.
- Drop the stale NATS dependency sentence from the env-configuration README; the
  definition only depends on common-integrations v1alpha2.
…o 0.2.0

The generated mapping now matches the 0.2.0 semantic bridge and release. The test that
pinned it to the 0.1.0 output now checks the legacy extension release and operations,
and a new test checks that the committed mapping equals the compiler output. The
nats-service Go, Python and TypeScript bindings follow the extension at 0.2.0.
Comment on lines +174 to +176
def test_committed_0_2_0_release_matches_the_compiler_output(self):
self.assertEqual(self.extension, read_document(ROOT / "releases/0.2.0/runtimeconditions.extension.yaml"))

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to have a test for one sepcific version?

…model emitter tests

The TypeScript and Java real-model tests hard-coded the v1alpha1 common-integrations id as
env-configuration's dependency. The committed bindings are now v1alpha2, so the dependency
check failed. The tests now take the id from the loaded common-integrations model.
@colinjlacy
colinjlacy merged commit 3050855 into runtimeconditions:main Nov 14, 2026
8 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