-
Notifications
You must be signed in to change notification settings - Fork 142
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
Publish 3.0.1 as v3.0.1-draft #995
Conversation
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]>
Signed-off-by: Arthit Suriyawongkul <[email protected]>
Co-authored-by: Alexios Zavras (zvr) <[email protected]> Signed-off-by: Arthit Suriyawongkul <[email protected]>
The new version of the spec-parser will generate as well
See #978 |
@puerco - Should we use commits for the actions rather than tags? |
Can change to uses: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332 #v4.1.7 |
Thanks @bact - this should resolve the possible security issue if the tag is changed. |
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]>
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]>
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]>
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]>
@zvr Note that I have modify the PR validation workflow |
I think the default shown should be the one we're working on, but this can be decided and changed later. |
Agree. Let's have this published first and we can start seeing updated contents and formats. Then made any necessary changes afterwards. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thank you. Content from |
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:
v3.0.1-draft
, usingdevelopment/v3.0.1
ofspdx-spec
andmain
ofspdx-model
actions/checkout
to v4 to prevent build warning of Node.js deprecationUse the generated
mkdocs-files.yml
from Use the actual list of model entries #978Notes
After v3.0.1 is released, another PR can be made to publish
v3.0.1
, usingdevelopment/v3.0.1
ofspdx-spec
and3.0.1
ofspdx-model
-- also assign the versionv3.0.1
with two aliasesv3.0.1-draft
andlatest
.run: mike deploy -u -b gh-pages -p v3.0.1 v3.0.1-draft latest