nsaspy/zara-plugins
1
0
Fork 0
Code Issues 10 Pull requests 297 Projects Releases Packages Wiki Activity Actions

registry: reject contradictory service metadata identities #391

Open
nsaspy wants to merge 9 commits from rage/179-strict-service-metadata into main
pull from: rage/179-strict-service-metadata
merge into: nsaspy:main
Conversation 0 Commits 9 Files changed 2 +78 -15
nsaspy commented 2026-09-08 02:19:41 +00:00
Owner
Copy link

Closes #179.

RAGE transaction:

  • RED 052cf6e6: contradictory literal PluginMetadata names/versions were accepted when the expected value was merely present.
  • implementation: require discovered metadata names and versions to be exact singleton identities matching the registry.
  • full registry gating then exposed an unrelated false-positive in fallback version evidence: API_VERSION values were being mixed with plugin versions. The fallback now accepts VERSION / *PLUGIN_VERSION only and explicitly proves scoped plugin constants while excluding *API_VERSION.

Scope stays static and import-free; no Zara Core/runtime changes.

Gate: exact-head registry/compatibility tests, full nix flake check, generated package builds.

Closes #179. RAGE transaction: - RED `052cf6e6`: contradictory literal `PluginMetadata` names/versions were accepted when the expected value was merely present. - implementation: require discovered metadata names and versions to be exact singleton identities matching the registry. - full registry gating then exposed an unrelated false-positive in fallback version evidence: `API_VERSION` values were being mixed with plugin versions. The fallback now accepts `VERSION` / `*PLUGIN_VERSION` only and explicitly proves scoped plugin constants while excluding `*API_VERSION`. Scope stays static and import-free; no Zara Core/runtime changes. Gate: exact-head registry/compatibility tests, full `nix flake check`, generated package builds.
test: prove scoped plugin version fallback
Some checks failed
CI / test (pull_request) Failing after 17s
Details
1f3d06bb8b
Some checks failed
CI / test (pull_request) Failing after 17s
Details
This pull request has changes conflicting with the target branch.
  • scripts/validate-registry.py
  • tests/test_validate_registry_service_metadata.py
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin rage/179-strict-service-metadata:rage/179-strict-service-metadata
git switch rage/179-strict-service-metadata

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff rage/179-strict-service-metadata
git switch rage/179-strict-service-metadata
git rebase main
git switch main
git merge --ff-only rage/179-strict-service-metadata
git switch rage/179-strict-service-metadata
git rebase main
git switch main
git merge --no-ff rage/179-strict-service-metadata
git switch main
git merge --squash rage/179-strict-service-metadata
git switch main
git merge --ff-only rage/179-strict-service-metadata
git switch main
git merge rage/179-strict-service-metadata
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
accessibility
Barrier affecting people with disabilities

  
bug
Something isn't working

  
documentation
Improvements or additions to documentation

  
duplicate
This issue or pull request already exists

  
enhancement
New feature or request

  
good first issue
Good for newcomers

  
help wanted
Extra attention is needed

  
invalid
This doesn't seem right

  
question
Further information is requested

  
security

   
wontfix
This will not be worked on

No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
security
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nsaspy/zara-plugins!391
No description provided.