Repository navigation
chore: update workflow references to upstream tooling - #54
Merged
hdamker-bot merged 2 commits intoApr 1, 2026
Merged
Conversation
hdamker-bot
approved these changes
Apr 1, 2026
hdamker
added a commit
that referenced
this pull request
Apr 1, 2026
* Update release-automation.yml (#50) * test: add sample-service API with external $ref to common schemas Adds sample-service.yaml (from Commonalities restructure-artifacts) which uses $ref to ../common/CAMARA_common.yaml for shared schemas, error responses, headers, and security schemes. Smoke test for bundling pipeline (WP-06.08, DEC-021). * test: add sample-service to release-plan.yaml Declares sample-service as alpha 0.1.0 alongside existing release-test. * Update release automation workflow version * Rename workflow and update reusable workflow reference (#53) Updated the workflow name and changed the repository reference for the reusable workflow. * chore: update workflow references to upstream tooling (#54) * chore: update workflow references to upstream tooling * test: add sample-service feature file for validation testing --------- Co-authored-by: hdamker-bot <herbert.damker@gmail.com>
hdamker
added a commit
to hdamker/ReleaseTest
that referenced
this pull request
Apr 1, 2026
Lost during workflow reference update in PR camaraproject#54. Without this, org secrets (RELEASE_APP_PRIVATE_KEY) are not passed to the reusable workflow.
hdamker-bot
pushed a commit
that referenced
this pull request
Apr 1, 2026
Lost during workflow reference update in PR #54. Without this, org secrets (RELEASE_APP_PRIVATE_KEY) are not passed to the reusable workflow.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
repository management, tests
What this PR does / why we need it:
Updates the validation and release automation caller workflows to reference
camaraproject/tooling@validation-framework(upstream) instead ofhdamker/tooling@validation-framework(fork). This is needed because thevalidation-frameworkbranch has been published to upstream tooling for integration testing.Also adds a minimal gherkin test definition for the sample-service API to enable validation framework testing of the gherkin-lint engine across both APIs.
Which issue(s) this PR fixes:
Part of validation framework v1 integration testing (ReleaseManagement#448).
Special notes for reviewers:
The
validation-frameworkbranch now exists oncamaraproject/tooling. This PR makes the test repo reference that upstream branch instead of the fork.Changelog input
Additional documentation