oauth2MetadataUrl

.github/CODEOWNERS

@@ -0,0 +1,11 @@
+# Global Repo Owners
+* @oai/openapi-maintainers @oai/tsc
+
+# Specification Versions
+/versions/ @oai/tsc
+
+# Protect specific top level files
+/MAINTAINERS.md @oai/tsc
+/TOB.md @oai/tsc
+/GOVERNANCE.md @oai/tsc
+/LICENSE @oai/tsc

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,17 @@
+blank_issues_enabled: true
+contact_links:
+  - name: OpenAPI Specification
+    url: https://spec.openapis.org/oas/latest.html
+    about: View the latest version of the specification
+  - name: Getting started documentation
+    url: https://learn.openapis.org
+    about: Learn about the OpenAPI Specification
+  - name: OpenAPI Tooling
+    url: https://tools.openapis.org
+    about: Open-source and commercial tools for OpenAPI
+  - name: OpenAPI Initiative Registry
+    url: https://spec.openapis.org/registry/index.html
+    about: Registry of formats, extension namespaces etc.
+  - name: OpenAPI Initiative Slack
+    url: https://communityinviter.com/apps/open-api/openapi
+    about: Join our online community.

.github/dependabot.yml

@@ -0,0 +1,12 @@
+version: 2
+updates:
+- package-ecosystem: github-actions
+  directory: "/"
+  schedule:
+    interval: daily
+  open-pull-requests-limit: 10
+- package-ecosystem: npm
+  directory: "/"
+  schedule:
+    interval: daily
+  open-pull-requests-limit: 10

.github/pull_request_template.md

@@ -0,0 +1,16 @@
+<!--
+Thank you for contributing to the OpenAPI Specification!
+
+Please make certain you are submitting your PR on the correct
+branch and file:
+
+* 3.0.x spec: v3.0.4-dev branch, versions/3.0.4.md
+* 3.1.x spec: v3.1.1-dev branch, versions/3.1.1.md
+* 3.2.0 spec: v3.2.0-dev branch, versions/3.2.0.md
+* 3.0 schema: main branch, schemas/v3.0/...
+* 3.1 schema: main branch, schemas/v3.1/...
+* registry templates: gh-pages branch, registry/...
+* registry contents: gh-pages branch, registries/...
+
+Note that we do not accept changes to published specifications.
+-->

.github/templates/agenda.md

@@ -1,19 +1,22 @@
-**NOTE: This meeting is on Thursday at 9am - 10am PT**
+**NOTE: weekly meetings happen on Thursdays at 9am - 10am Pacific.**
 
-Zoom Meeting link: [https://zoom.us/j/975841675](https://zoom.us/j/975841675?pwd=SUh4MjRLaEFKNlI3RElpWTdhRDVVUT09). Dial-in passcode: 763054
+This agenda gives visibility into discussion topics for the weekly Technical Developer Community (TDC) meetings. Sharing agenda items in advance allows people to plan to attend meetings where they have an interest in specific topics. 
 
-In order to give some more visibility into the topics we cover in the TDC meetings here is the planned agenda for the next meeting.  Hopefully this will allow people to plan to attend meetings for topics that they have an interest in.  And for folks who cannot attend they can comment on this issue prior to the meeting.  Feel free to suggest other potential agenda topics.
+Whether attending or not, **anyone can comment on this issue prior to the meeting to suggest topics or to add comments on planned topics or proposals**.
 
-**Please submit comments below for topics or proposals that you wish to present in the TDC meeting**
+Zoom: [https://zoom.us/j/975841675](https://zoom.us/j/975841675?pwd=SUh4MjRLaEFKNlI3RElpWTdhRDVVUT09), dial-in passcode: 763054
 
-The agenda backlog is currently maintained in issue #2482
+Participants must abide by our [Code-of-Conduct](https://github.com/OAI/OpenAPI-Specification/blob/main/CODE_OF_CONDUCT.md#code-of-conduct).
+
+![F10B5460-B4B3-4463-9CDE-C7F782202EA9](https://user-images.githubusercontent.com/21603/121568843-0b260900-ca18-11eb-9362-69fda4162be8.jpeg)
 
 | Topic | Owner | Decision/NextStep |
 |-------|---------|---------|  
 | | | |
-AOB (see below) | TDC | |
-New issues / PRs labelled [review](https://github.com/OAI/OpenAPI-Specification/labels/review) | @OAI/triage | |
-[New issues](https://github.com/search?q=repo%3Aoai%2Fopenapi-specification+is%3Aissue+comments%3A0+no%3Alabel+is%3Aopen) without response yet | @OAI/triage  | |
-
+Intros and governance meta-topics (5 mins) | TDC | |
+Reports from Special Interest Groups (5 mins) | SIG members | |
+Any other business (add comments below to suggest topics) | TDC | |
+[Approved spec PRs](https://github.com/OAI/OpenAPI-Specification/pulls?q=is%3Apr+is%3Aopen+review%3Aapproved) | TDC | |
+[New issues needing attention](https://github.com/search?q=repo%3Aoai%2Fopenapi-specification+is%3Aissue+comments%3A0+no%3Alabel+is%3Aopen) | @OAI/triage  | |
 
-/cc @OAI/tsc Please suggest items for inclusion
+/cc [@OAI/tsc](https://github.com/orgs/OAI/teams/tsc) please suggest items for inclusion.

.github/workflows/agenda.yaml

@@ -11,19 +11,37 @@ name: agenda
 
 on:
   schedule:
-    - cron: '0 9 * * 2'
+    - cron: '0 16 * * 4'
   workflow_dispatch: {}
-
+
+permissions:
+  issues: write
+  contents: read
+
 jobs:
   agenda:
+    if: github.repository == 'OAI/OpenAPI-Specification'
     env:
       GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      TITLE_PREFIX: "Open Community (TDC) Meeting, "
+      LABEL: "Housekeeping"
+      POST_MEETING_CLOSE_DURATION_IN_DAYS: 10
 
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v1 # checkout repo content
+    - uses: actions/checkout@v4 # checkout repo content
+
+    # we want to close old agenda issues before creating a new one because there's a limit of 3 pinned items on a repo
+    - name: Close old agenda issues
+      run: gh issue list -l ${{ env.LABEL }} --author "app/github-actions" --json number,title | ConvertFrom-Json | Where-Object { $_.title -like "${{ env.TITLE_PREFIX }}*" -and ([datetime]::UtcNow - [datetime]::Parse([regex]::Replace($_.title.Replace("${{ env.TITLE_PREFIX }}", ""), "\([^)]+\)", ""))) -ge [timespan]::FromDays([int]::Parse("${{ env.POST_MEETING_CLOSE_DURATION_IN_DAYS }}"))} | ForEach-Object { gh issue close $_.number && gh issue unpin $_.number }
+      shell: pwsh
 
     - name: Create agenda issue
-      run: gh issue create -l Housekeeping -t "Open Community (TDC) Meeting, `date --date='next Thu' +'%A %d %B %Y'`" -F .github/templates/agenda.md
+      run: |
+        $nextThursday = @(@(1..8) | % {$(Get-Date).AddDays($_)} | ? {$_.DayOfWeek -ieq "Thursday"})[0].ToString("dddd dd MMMM yyyy", [CultureInfo]::InvariantCulture)
+        $result = gh issue create -l ${{ env.LABEL }} -t "${{ env.TITLE_PREFIX }}$nextThursday" -F .github/templates/agenda.md
+        gh issue pin $result
+      shell: pwsh
+
 

.github/workflows/convert-examples-to-json.yaml

@@ -24,8 +24,12 @@ jobs:
     steps:
     - uses: actions/checkout@v2 # checkout repo content
 
+    - uses: actions/setup-node@v4 # setup Node.js
+      with:
+        node-version: '20.x'
+
     - name: Install dependencies
-      run: npm i
+      run: npm ci
 
     - name: convert YAML examples to JSON
       run: find examples/v3* -type f -name "*.yaml" | xargs node scripts/yaml2json/yaml2json.js
@@ -36,7 +40,7 @@ jobs:
         git --no-pager -c color.diff=always diff --staged
 
     - name: Create Pull Request
-      uses: peter-evans/create-pull-request@v3
+      uses: peter-evans/create-pull-request@v5
       with:
         token: ${{ secrets.GITHUB_TOKEN }}
         branch: update-json-examples

.github/workflows/inactive-issues.yml

@@ -0,0 +1,36 @@
+on:
+  issues:
+    types: labeled
+  workflow_dispatch:
+  schedule:
+    - cron: '*/5 * * * *'
+
+permissions:
+  issues: write
+  contents: read
+
+name: Label and close issues with no recent activity
+
+env:
+  GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+  NEEDS_ATTENTION_LABEL: "Needs attention"
+  NEEDS_AUTHOR_FEEDBACK_LABEL: "Needs author feedback"
+  NO_RECENT_ACTIVITY_LABEL: "No recent activity"
+  NO_RECENT_ACTIVITY_DURATION_IN_DAYS: 7
+  NO_RECENT_ACTIVITY_DURATION_CLOSE_IN_DAYS: 28
+  ORG_NAME: ${{ github.repository_owner }}
+  REPO_NAME: ${{ github.event.repository.name }}
+  NO_RECENT_ACTIVITY_COMMENT: "This issue has been labeled with `No recent activity` because there has been no recent activity. It will be closed if no further activity occurs within 28 days. Please re-open this issue or open a new one after this delay if you need to."
+
+
+jobs:
+  run:
+    if: github.repository == 'OAI/OpenAPI-Specification'
+    runs-on: ubuntu-latest
+    name: Label issues with no recent activity
+    steps:
+      - uses: actions/checkout@v4
+      - run: scripts/label-no-recent.ps1
+        shell: pwsh
+      - run: scripts/close-no-recent.ps1
+        shell: pwsh

.github/workflows/respec.yaml

@@ -21,12 +21,18 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2 # checkout main branch
+    - uses: actions/checkout@v4 # checkout main branch
+      with:
+        fetch-depth: 0
 
+    - uses: actions/setup-node@v4 # setup Node.js
+      with:
+        node-version: '20.x'
+
     - name: Install dependencies
-      run: npm i
+      run: npm ci
 
-    - uses: actions/checkout@v2 # checkout gh-pages branch
+    - uses: actions/checkout@v4 # checkout gh-pages branch
       with:
         ref: gh-pages
         path: deploy
@@ -35,7 +41,7 @@ jobs:
       run: scripts/md2html/build.sh
 
     - name: Create Pull Request
-      uses: peter-evans/create-pull-request@v3
+      uses: peter-evans/create-pull-request@v6
       with:
         token: ${{ secrets.GITHUB_TOKEN }}
         branch: update-respec-version

.github/workflows/schema-tests.yaml

@@ -0,0 +1,35 @@
+name: schema-test
+
+# Author: @MikeRalphson / runs @jdesrosiers tests
+# Issue: https://github.com/OAI/OpenAPI-Specification/pull/2489
+
+#
+# This workflow runs the npm test script to validate passing and failing
+# testcases for the metaschema.
+#
+
+# run this on push to any branch and creation of pull-requests
+on: 
+  push: {}
+  pull_request: {}
+  workflow_dispatch: {}
+
+jobs:
+  test:
+
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v4 # checkout repo content
+      with:
+        fetch-depth: 0
+    - uses: actions/setup-node@v4 # setup Node.js
+      with:
+        node-version: '20.x'
+    - name: Install dependencies from main
+      run: |
+        git checkout remotes/origin/main -- package.json package-lock.json
+        npm ci
+    - name: Run tests
+      run: npm run test
+

.github/workflows/validate-markdown.yaml

@@ -18,10 +18,15 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-    - uses: actions/checkout@v2 # checkout repo content
-    - uses: actions/setup-node@v1 # setup Node.js
+    - uses: actions/checkout@v4 # checkout repo content
       with:
-        node-version: '12.x'
+        fetch-depth: 0
+    - name: use the javascript environment from main
+      run: |
+        git checkout remotes/origin/main -- package.json package-lock.json
+    - uses: actions/setup-node@v4 # setup Node.js
+      with:
+        node-version: '20.x'
     - name: Validate markdown
-      run: npx mdv versions/3.*.md
+      run: npx --yes mdv versions/3.*.md
 

.gitignore

@@ -5,7 +5,6 @@
 target
 atlassian-ide-plugin.xml
 node_modules/
-package-lock.json
 deploy/
 history
 Gemfile.lock

CODE_OF_CONDUCT.md

@@ -94,13 +94,50 @@ offender, banning the offender from various online spaces (temporary or
 permanent), removing the offender from an event with no refund, or other
 options deemed appropriate.
 
-Further details of specific enforcement policies are currently being
-drafted. When these details are completed we will post updates to our
-website for transparency.
-
-Project maintainers who do not report possible incidents or follow
-responses in good faith may face temporary or permanent repercussions as
-determined by the Code of Conduct Committee.
+Enforcement Guidelines
+----------------------
+
+The Code of Conduct committee will follow these Enforcement Guidelines in 
+determining the consequences for any action they deem in violation of this 
+Code of Conduct:
+
+#### 1. Correction
+Community Impact: Use of inappropriate language or other behavior deemed 
+unprofessional or unwelcome in the community.
+
+Consequence: A private, written warning from the Code of Conduct committee, 
+providing clarity around the nature of the violation and an explanation of 
+why the behavior was inappropriate. A public apology may be requested.
+
+#### 2. Warning
+Community Impact: A violation through a single incident or series of 
+actions.
+
+Consequence: A warning with consequences for continued behavior. No 
+interaction with the people involved, including unsolicited interaction 
+with the Code of Conduct committee, for a specified period of time. This 
+includes avoiding interactions in community spaces as well as external 
+channels like social media. Violating these terms may lead to a temporary 
+or permanent ban.
+
+#### 3. Temporary Ban
+Community Impact: A serious violation of community standards, including 
+sustained inappropriate behavior.
+
+Consequence: A temporary ban from any sort of interaction or public 
+communication with the community for a specified period of time. No 
+public or private interaction with the people involved, including 
+unsolicited interaction with the Code of Conduct committee, is allowed 
+during this period. Violating these terms may lead to a permanent ban.
+
+#### 4. Permanent Ban
+Community Impact: Demonstrating a pattern of violation of community 
+standards, including sustained inappropriate behavior, harassment of 
+an individual, or aggression toward or disparagement of classes of 
+individuals.
+
+Consequence: A permanent ban from any sort of public interaction 
+within the community.
 
 ### Events