Skip to content

Conversation

@CarstenWickner
Copy link
Contributor

Support for Draft 2020-12 in the victools:jsonschema-generator library was introduced end of 2021; support for Draft 6 even before that.

Merely updating the reference here.

Copy link
Collaborator

@benjagm benjagm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Carsten. Thanks a lot for updating this information!!
Have a great week!

Julian added a commit that referenced this pull request Nov 6, 2023
This doesn't *seem* like it should matter -- in that this workflow was
tested as-is on a different repository as part of building it, and ran
successfully. Furthermore, the docs for the permissions property in
GitHub (at https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs)
say:

    You can use permissions either as a top-level key, to apply to all
    jobs in the workflow, or within specific jobs. When you add the
    permissions key within a specific job, all actions and run commands
    within that job that use the GITHUB_TOKEN gain the access rights you
    specify.

so, top-level seems like it's supposed to work fine.

And yet, in the "Set up job" step of #206, the permissions for
PullRequest are shown as:

    PullRequest: read

(https://github.com/json-schema-org/website/actions/runs/6762327321/job/18401399964?pr=206#step:1:18
though that link won't last forever).

Let's see at least if this changes that...

Refs: #173
@benjagm benjagm merged commit 6aea4e9 into json-schema-org:main Nov 16, 2023
@benjagm
Copy link
Collaborator

benjagm commented Nov 16, 2023

Thanks a lot for updating the information @CarstenWickner !

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.

2 participants