Skip to content

Update ReSpec versions for Arazzo #3890

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Conversation

ncaidin
Copy link
Contributor

@ncaidin ncaidin commented Jun 7, 2024

This pull request is automatically triggered by GitHub action respec.

The versions/v*.md files of the Arazzo Specification have changed, so the HTML files are automatically being regenerated.

@frankkilcommins
Copy link
Contributor

frankkilcommins commented Jun 7, 2024

@handrews @Bellangelo if you like what you see re the improved RFC fragments links, I can issue a PR against the OAS repo for the script changes for #3863.

See https://github.com/OAI/Arazzo-Specification/pull/199/files for more details

@github-actions github-actions bot force-pushed the update-respec-version branch from 557d001 to ea03525 Compare June 7, 2024 18:51
@github-actions github-actions bot closed this Jun 7, 2024
@handrews
Copy link
Member

handrews commented Jun 7, 2024

@frankkilcommins any idea why the github-actions bot closed this?

@handrews
Copy link
Member

handrews commented Jun 7, 2024

Reopening so people see this, but let's not merge until we figure out what the bot was doing.

@handrews
Copy link
Member

handrews commented Jun 7, 2024

or not, because the bot deleted the branch. The AI revolt is here! All is lost! 😛

@frankkilcommins
Copy link
Contributor

frankkilcommins commented Jun 7, 2024

@handrews I think I see the problem. There is a clash with the respec action on the OpenAPI-Specification repo and the Arazzo-Specification. Both jobs create branches of the same name (update-respec-version) and take it over if already existing.

See run https://github.com/OAI/OpenAPI-Specification/actions/runs/9421774871/job/25956585879 which was triggered by some of your good work.

I'll create an issue on the Arazzo repo to use a specification specific branch name to avoid cross spec repo collisions.

@frankkilcommins
Copy link
Contributor

See OAI/Arazzo-Specification#200

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants