Skip to content

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Nov 7, 2024

This pull request is automatically triggered by GitHub action schema-publish.
The schemas/**/*.yaml files have changed and JSON files are automatically generated.

@github-actions github-actions bot added Housekeeping Schema changes related to the schema(s) labels Nov 7, 2024
@github-actions github-actions bot changed the title Publish OpenAPI Metaschema Iterations Publish OpenAPI Schema Iterations Nov 12, 2024
@github-actions github-actions bot force-pushed the publish-schema-iteration branch from a2bef07 to 4dbaf41 Compare November 12, 2024 16:51
@github-actions github-actions bot requested a review from ralfhandl November 12, 2024 19:40
@github-actions github-actions bot requested a review from ralfhandl November 14, 2024 09:38
ralfhandl
ralfhandl previously approved these changes Nov 14, 2024
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@karenetheridge
Copy link
Member

is it possible to preview the about-to-be-published files before they are actually published?

@lornajane lornajane merged commit 4089a5d into gh-pages Nov 21, 2024
@lornajane lornajane deleted the publish-schema-iteration branch November 21, 2024 17:11
@ralfhandl
Copy link
Contributor

is it possible to preview the about-to-be-published files before they are actually published?

Hi @karenetheridge, which kind of preview would you expect?

The publishing process is

  • Merge changes to the schema YAML files into main - this allows "previewing" the changes in a PR, for example main: 3.1 schema - link to minor spec version #4206
  • Create PR like this one for publishing schema JSON files to gh-pages - this allows "previewing" the new JSON files in the PR, via "View file" or "Raw"

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

Labels

Housekeeping Schema changes related to the schema(s)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants