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.

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

Publish 3.0.1 as v3.0.1-draft #995

Merged
merged 28 commits into from
Jul 30, 2024

Conversation

bact
Copy link
Collaborator

@bact bact commented Jul 18, 2024

What this PR do?

Loosely applying steps 5, 7, and 8 in #950 (comment) but using v3.0.1-draft as a version for now while 3.0.1 is still in development.

  • in .github/workflows/publish_v3.yml:

    • Publish v3.0.1-draft, using development/v3.0.1 of spdx-spec and main of spdx-model
    • Update actions/checkout to v4 to prevent build warning of Node.js deprecation
  • Use the generated mkdocs-files.yml from Use the actual list of model entries #978

Notes

After v3.0.1 is released, another PR can be made to publish v3.0.1, using development/v3.0.1 of spdx-spec and 3.0.1 of spdx-model -- also assign the version v3.0.1 with two aliases v3.0.1-draft and latest.

  • run: mike deploy -u -b gh-pages -p v3.0.1 v3.0.1-draft latest

bact added 8 commits July 18, 2024 08:14
Signed-off-by: Arthit Suriyawongkul <[email protected]>
Signed-off-by: Arthit Suriyawongkul <[email protected]>
Signed-off-by: Arthit Suriyawongkul <[email protected]>
Make the argument orders the same order as in "mike deploy -h" for easy ref.

Signed-off-by: Arthit Suriyawongkul <[email protected]>
Signed-off-by: Arthit Suriyawongkul <[email protected]>
Signed-off-by: Arthit Suriyawongkul <[email protected]>
Signed-off-by: Arthit Suriyawongkul <[email protected]>
Signed-off-by: Arthit Suriyawongkul <[email protected]>
Co-authored-by: Alexios Zavras (zvr) <[email protected]>
Signed-off-by: Arthit Suriyawongkul <[email protected]>
@bact
Copy link
Collaborator Author

bact commented Jul 24, 2024

The new version of the spec-parser will generate as well mkdocs-files.yml which contains a list of model files.

mkdocs.yml has to be modified to use that:

  • The model subsection under nav has to be modified to an empty list.
  • After the spec-parser run, copy the content from mkdocs-files.yml and put it in the model subsection.

See #978

@goneall
Copy link
Member

goneall commented Jul 24, 2024

@puerco - Should we use commits for the actions rather than tags?

@bact
Copy link
Collaborator Author

bact commented Jul 24, 2024

Can change to

uses: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332  #v4.1.7

@goneall
Copy link
Member

goneall commented Jul 25, 2024

Can change to

uses: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332  #v4.1.7

Thanks @bact - this should resolve the possible security issue if the tag is changed.

bact added 10 commits July 25, 2024 03:25
Signed-off-by: Arthit Suriyawongkul <[email protected]>
Signed-off-by: Arthit Suriyawongkul <[email protected]>
- Remove model file list from mkdocs.yml
- Generate mkdocs-final.yml from base mkdocs.yml and mkdocs-files.yml
- Let mike deploy using mkdocs-final.yml

Signed-off-by: Arthit Suriyawongkul <[email protected]>
Update PR validation workflow to use mkdocs-files.yml

Signed-off-by: Arthit Suriyawongkul <[email protected]>
Signed-off-by: Arthit Suriyawongkul <[email protected]>
To avoid confusion with file path inside -e expression

Signed-off-by: Arthit Suriyawongkul <[email protected]>
Signed-off-by: Arthit Suriyawongkul <[email protected]>
Signed-off-by: Arthit Suriyawongkul <[email protected]>
bact added 6 commits July 25, 2024 18:44
Signed-off-by: Arthit Suriyawongkul <[email protected]>
Signed-off-by: Arthit Suriyawongkul <[email protected]>
Regardless if mkdocs-files.yml has a standard one blank line at the end of file or not, we insert one, just in case.

Signed-off-by: Arthit Suriyawongkul <[email protected]>
Add mkdocs files and links validation

Files need to be somewhere, if not in nav, then in draft_docs.

Signed-off-by: Arthit Suriyawongkul <[email protected]>
Signed-off-by: Arthit Suriyawongkul <[email protected]>
@bact
Copy link
Collaborator Author

bact commented Jul 26, 2024

@zvr publish_v3.yml publication workflow is now using the actual list of model entries generated by spec-parser. See lines 56-69.

Note that I have modify the PR validation workflow validate_pull_request.yml to do the same (using the generated list of model entries). This is necessary to have this PR pass all the checks.

@zvr
Copy link
Member

zvr commented Jul 26, 2024

I think the default shown should be the one we're working on, but this can be decided and changed later.
Waiting for another approval to push and deploy this.

@bact
Copy link
Collaborator Author

bact commented Jul 26, 2024

Agree. Let's have this published first and we can start seeing updated contents and formats. Then made any necessary changes afterwards.

Copy link
Member

@goneall goneall left a comment

Choose a reason for hiding this comment

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

LGTM

@goneall goneall merged commit 048daca into spdx:development/v3.0.1 Jul 30, 2024
3 checks passed
@bact
Copy link
Collaborator Author

bact commented Jul 30, 2024

Thank you. Content from development/v3.0.1 is now published at https://spdx.github.io/spdx-spec/v3.0.1-draft/

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.

3 participants