Skip to content

chore: follow the Falcon release numbers, starting at 1.0.5 - #4

Merged
NaySurGithub merged 1 commit into
mainfrom
chore/follow-falcon-version
Nov 8, 2026
Merged

NaySurGithub merged 1 commit into
mainfrom
chore/follow-falcon-version

Conversation

@NaySurGithub

Copy link
Copy Markdown
Contributor

Summary

The plugin API now follows the Falcon release numbers. It goes from 1.3.3 to 1.0.5, the next Falcon release; later releases bump it together with Falcon (1.0.6, 1.0.7…).

  • falcon_api.h: FALCON_API_VERSION_MINOR 0, FALCON_API_VERSION_PATCH 5
  • java/pom.xml, the Java example (pom.xml, plugin.json), wasm/falcon.wit (falcon:plugin@1.0.5) and the README samples and badge

Compatibility: the server accepts a plugin with the same major and a minor up to its own, so a plugin that declares "api-version": "1.3.x" is refused by a server built on this API; it must declare 1.0.5 (or lower) instead. Wasm plugins import falcon:plugin@1.0.5 and need a rebuild. Falcon must update its pin and its Wasm import strings (@1.3.3) at the same time.

Test plan

  • Falcon builds with the new pin and loads the native, Java, .NET and Wasm examples

@NaySurGithub
NaySurGithub merged commit 8b15b10 into main Nov 8, 2026
7 of 10 checks passed
@NaySurGithub
NaySurGithub deleted the chore/follow-falcon-version branch November 8, 2026 16:54
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.

1 participant