Skip to content
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.

Sign up for GitHub

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

Jump to bottom

docs: adapting release process to new definition setup #659

Merged
merged 9 commits into from
Jun 17, 2022
Merged

docs: adapting release process to new definition setup #659

Changes from all commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
15a2283
Adapting release process
jonaslagoni Nov 25, 2021
a44ed7a
Adapting release process
jonaslagoni Dec 9, 2021
48cdbbf
Merge branch 'master' into feature/change_spec_json_release_process
jonaslagoni Mar 14, 2022
ba51a42
Merge branch 'master' into feature/change_spec_json_release_process
jonaslagoni May 17, 2022
682e3f8
Update RELEASE_PROCESS.md
jonaslagoni May 17, 2022
795c1f5
Update RELEASE_PROCESS.md
jonaslagoni May 17, 2022
4973d4f
Update RELEASE_PROCESS.md
jonaslagoni May 18, 2022
f8622cd
Merge branch 'master' into feature/change_spec_json_release_process
jonaslagoni Jun 8, 2022
c0a5517
Merge branch 'master' into feature/change_spec_json_release_process
fmvilas Jun 17, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions RELEASE_PROCESS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -133,13 +133,13 @@ An example of doing this is:
#### Step 3.4 - Create a new JSON schema file for the new version
Repository: [spec-json-schemas](https:/asyncapi/spec-json-schemas)

The new file should be created in the `schemas/` folder in the [spec-json-schemas](https:/asyncapi/spec-json-schemas) repository.
To create a new version, please read [Creating a new version](https:/asyncapi/spec-json-schemas#creating-a-new-version).

It should be named with the version of the new release, and a link should be added to the `index.js` file (in the same repository).

An example of doing this is:
- this [commit from the 2.3.0 release](https:/dalelane/spec-json-schemas/commit/9cff7798ac42f609927e1cb9e532ff16d360ab99)
- this [pull request from the 2.3.0 release](https:/asyncapi/spec-json-schemas/pull/139)
- this [commit from the 3.0.0 release](https:/asyncapi/spec-json-schemas/pull/221/files)
- this [pull request from the 3.0.0 release](https:/asyncapi/spec-json-schemas/pull/221)

#### Step 3.5 - Update the list of AsyncAPI schema MIME types with the new version
Repository: [parser-js](https:/asyncapi/parser-js)
Expand Down