Skip to content

Auto update sphinx theme css files #291

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
Merged
merged 2 commits into from
Apr 2, 2025
Merged

Auto update sphinx theme css files #291

merged 2 commits into from
Apr 2, 2025

Conversation

unidevel
Copy link
Contributor

@unidevel unidevel commented Feb 11, 2025 •
edited
Loading

This PR will update the siteConfig.js automatically.
Also no need to replace @support in the css file manually.

Address the issue in step 5 => https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)#step-5-publish-docs-website

To make auto fix when commit working, please run

cd website; yarn install

Then commit the newly added css files.

Usually when developer test the doc generation locally before commit, the siteConfig.js will be auto fixed.

Also provide the manual comamnd update siteConfig.js

cd website; yarn update-site-config

@unidevel
Copy link
Contributor Author

@ZacBlanco @wanglinsong can you help to review this PR, thanks.

ZacBlanco
ZacBlanco reviewed Feb 17, 2025
View reviewed changes
@unidevel unidevel requested a review from ZacBlanco March 10, 2025 19:08
@unidevel
Copy link
Contributor Author

@ZacBlanco @wanglinsong seems I don't have access to merge PR, can you help to merge this PR, thanks.

@wanglinsong wanglinsong requested a review from alileclerc March 12, 2025 16:59
@unidevel unidevel mentioned this pull request Mar 13, 2025
Merged
6 tasks
@unidevel
Copy link
Contributor Author

unidevel commented Mar 14, 2025 •
edited
Loading

Validated by the new release action =>https://github.com/unix280/presto/actions/runs/13844025717/job/38739241705#step:8:21

Found CSS files: [
  '    "static/sphinx_immaterial_theme.359ec555e2989f00f.min.css",',
  '    "static/sphinx_immaterial_theme.37dfeca1a5899a14e.min.css",',
  '    "static/sphinx_immaterial_theme.8bc14be58eddc636f.min.css",'
]

Auto added the css files and updated with the script in @tdcmeehan 's release doc

sed -ibak -e 's/@supports selector(.*11\.5rem)}}//' website/static/docs/current/_static/sphinx_immaterial_theme.*.css

@unidevel unidevel mentioned this pull request Mar 28, 2025
Merged
6 tasks
wanglinsong
wanglinsong requested changes Apr 1, 2025
View reviewed changes
Copy link
Member

@wanglinsong wanglinsong left a comment

Choose a reason for hiding this comment

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

Please also generate package-lock.json file and check it in.

website/updateSiteConfig.js Outdated
process.exit(0);
}

updateSphinxThemeFiles().catch(console.error);
Copy link
Member

Choose a reason for hiding this comment

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

Please add a newline.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

@unidevel unidevel force-pushed the auto_update_theme_files branch from 4379a97 to f0beb13 Compare April 2, 2025 07:07
@unidevel
Copy link
Contributor Author

unidevel commented Apr 2, 2025

Please also generate package-lock.json file and check it in.

Since we are using yarn in the github action, I generated yarn.lock instead of package-lock.json

prestodb.github.io/.github/workflows/publish.yml

Line 19 in f72b3e1

run: cd website && yarn install && yarn build

@unidevel unidevel requested a review from wanglinsong April 2, 2025 07:10
wanglinsong
wanglinsong approved these changes Apr 2, 2025
View reviewed changes
Copy link
Member

@wanglinsong wanglinsong left a comment

Choose a reason for hiding this comment

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

LGTM

@wanglinsong wanglinsong merged commit 8f81822 into prestodb:source Apr 2, 2025
3 checks passed
unidevel added a commit to prestodb/presto that referenced this pull request Apr 9, 2025
@unidevel
Add github action to publish artifacts for presto stable release (#24821
899f740 
)

## Description

This is a follow up of PR #24697,
seperate the github release actions into 2 PRs. This is the second one -
publish release artifacts like jars, docker images, websites, etc.

The document of stable release process can be found in
https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)

<!---Describe your changes in detail-->
Prior to the coming release, there were 5 steps:

- [Step 1 - Create a release branch and increment the version in the
master
branch](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)#step-1-create-a-release-branch-and-increment-the-version-in-the-master-branch)
- [Step 2 - Create release notes
PR](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months))
- [Step 3: clean up the
tag](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)#step-3-clean-up-the-tag)
- [Step 4: Publish Maven and Docker
artifacts](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)#step-4-publish-maven-and-docker-artifacts)
- [Step 5: Publish docs
website](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)#step-5-publish-docs-website)

### Action "Presto Stable Release -Publish"

<img width="969" alt="presto_release_publish_workflow"
src="https://github.com/user-attachments/assets/31e941ac-c3b9-4a2d-9660-1e9bfaaf2e26"
/>

- [Step 3: clean up the
tag](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)#step-3-clean-up-the-tag)
- [Step 4: Publish Maven and Docker
artifacts](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)#step-4-publish-maven-and-docker-artifacts)
- [Step 5: Publish docs
website](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)#step-5-publish-docs-website)

#### Parameters

<img width="309" alt="presto_release_publish_inputs"
src="https://github.com/user-attachments/assets/54e18451-e99c-43b0-9921-a90983edd592"
/>


#### Jobs

![image](https://github.com/user-attachments/assets/4fafe966-92df-44df-a06a-b013fd5b806c)


This PR required
prestodb/presto-release-tools#47,
prestodb/prestodb.github.io#291 to be merged and
released a new version`presto-release-tools` of before using these 2
actions

## Motivation and Context

## Impact
Presto stable release

## Test Plan
- Tested with my env
- Publish => https://github.com/unix280/presto/actions/runs/13844025717
- Test with new release 0.292 after merged

## Contributor checklist

- [ ] Please make sure your submission complies with our [contributing
guide](https://github.com/prestodb/presto/blob/master/CONTRIBUTING.md),
in particular [code
style](https://github.com/prestodb/presto/blob/master/CONTRIBUTING.md#code-style)
and [commit
standards](https://github.com/prestodb/presto/blob/master/CONTRIBUTING.md#commit-standards).
- [ ] PR description addresses the issue accurately and concisely. If
the change is non-trivial, a GitHub Issue is referenced.
- [ ] Documented new properties (with its default value), SQL syntax,
functions, or other functionality.
- [ ] If release notes are required, they follow the [release notes
guidelines](https://github.com/prestodb/presto/wiki/Release-Notes-Guidelines).
- [ ] Adequate tests were added if applicable.
- [ ] CI passed.

## Release Notes

```
== NO RELEASE NOTE ==
```
j-sund pushed a commit to j-sund/presto-rcos that referenced this pull request Apr 10, 2025
@unidevel @j-sund
Add github action to publish artifacts for presto stable release (pre…
ea3af10 
…stodb#24821)

## Description

This is a follow up of PR prestodb#24697,
seperate the github release actions into 2 PRs. This is the second one -
publish release artifacts like jars, docker images, websites, etc.

The document of stable release process can be found in
https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)

<!---Describe your changes in detail-->
Prior to the coming release, there were 5 steps:

- [Step 1 - Create a release branch and increment the version in the
master
branch](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)#step-1-create-a-release-branch-and-increment-the-version-in-the-master-branch)
- [Step 2 - Create release notes
PR](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months))
- [Step 3: clean up the
tag](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)#step-3-clean-up-the-tag)
- [Step 4: Publish Maven and Docker
artifacts](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)#step-4-publish-maven-and-docker-artifacts)
- [Step 5: Publish docs
website](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)#step-5-publish-docs-website)

### Action "Presto Stable Release -Publish"

<img width="969" alt="presto_release_publish_workflow"
src="https://github.com/user-attachments/assets/31e941ac-c3b9-4a2d-9660-1e9bfaaf2e26"
/>

- [Step 3: clean up the
tag](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)#step-3-clean-up-the-tag)
- [Step 4: Publish Maven and Docker
artifacts](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)#step-4-publish-maven-and-docker-artifacts)
- [Step 5: Publish docs
website](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)#step-5-publish-docs-website)

#### Parameters

<img width="309" alt="presto_release_publish_inputs"
src="https://github.com/user-attachments/assets/54e18451-e99c-43b0-9921-a90983edd592"
/>


#### Jobs

![image](https://github.com/user-attachments/assets/4fafe966-92df-44df-a06a-b013fd5b806c)


This PR required
prestodb/presto-release-tools#47,
prestodb/prestodb.github.io#291 to be merged and
released a new version`presto-release-tools` of before using these 2
actions

## Motivation and Context

## Impact
Presto stable release

## Test Plan
- Tested with my env
- Publish => https://github.com/unix280/presto/actions/runs/13844025717
- Test with new release 0.292 after merged

## Contributor checklist

- [ ] Please make sure your submission complies with our [contributing
guide](https://github.com/prestodb/presto/blob/master/CONTRIBUTING.md),
in particular [code
style](https://github.com/prestodb/presto/blob/master/CONTRIBUTING.md#code-style)
and [commit
standards](https://github.com/prestodb/presto/blob/master/CONTRIBUTING.md#commit-standards).
- [ ] PR description addresses the issue accurately and concisely. If
the change is non-trivial, a GitHub Issue is referenced.
- [ ] Documented new properties (with its default value), SQL syntax,
functions, or other functionality.
- [ ] If release notes are required, they follow the [release notes
guidelines](https://github.com/prestodb/presto/wiki/Release-Notes-Guidelines).
- [ ] Adequate tests were added if applicable.
- [ ] CI passed.

## Release Notes

```
== NO RELEASE NOTE ==
```
pradeepvaka pushed a commit to pradeepvaka/presto that referenced this pull request Apr 11, 2025
@unidevel @pradeepvaka
Add github action to publish artifacts for presto stable release (pre…
c030d76 
…stodb#24821)

## Description

This is a follow up of PR prestodb#24697,
seperate the github release actions into 2 PRs. This is the second one -
publish release artifacts like jars, docker images, websites, etc.

The document of stable release process can be found in
https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)

<!---Describe your changes in detail-->
Prior to the coming release, there were 5 steps:

- [Step 1 - Create a release branch and increment the version in the
master
branch](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)#step-1-create-a-release-branch-and-increment-the-version-in-the-master-branch)
- [Step 2 - Create release notes
PR](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months))
- [Step 3: clean up the
tag](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)#step-3-clean-up-the-tag)
- [Step 4: Publish Maven and Docker
artifacts](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)#step-4-publish-maven-and-docker-artifacts)
- [Step 5: Publish docs
website](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)#step-5-publish-docs-website)

### Action "Presto Stable Release -Publish"

<img width="969" alt="presto_release_publish_workflow"
src="https://github.com/user-attachments/assets/31e941ac-c3b9-4a2d-9660-1e9bfaaf2e26"
/>

- [Step 3: clean up the
tag](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)#step-3-clean-up-the-tag)
- [Step 4: Publish Maven and Docker
artifacts](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)#step-4-publish-maven-and-docker-artifacts)
- [Step 5: Publish docs
website](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)#step-5-publish-docs-website)

#### Parameters

<img width="309" alt="presto_release_publish_inputs"
src="https://github.com/user-attachments/assets/54e18451-e99c-43b0-9921-a90983edd592"
/>


#### Jobs

![image](https://github.com/user-attachments/assets/4fafe966-92df-44df-a06a-b013fd5b806c)


This PR required
prestodb/presto-release-tools#47,
prestodb/prestodb.github.io#291 to be merged and
released a new version`presto-release-tools` of before using these 2
actions

## Motivation and Context

## Impact
Presto stable release

## Test Plan
- Tested with my env
- Publish => https://github.com/unix280/presto/actions/runs/13844025717
- Test with new release 0.292 after merged

## Contributor checklist

- [ ] Please make sure your submission complies with our [contributing
guide](https://github.com/prestodb/presto/blob/master/CONTRIBUTING.md),
in particular [code
style](https://github.com/prestodb/presto/blob/master/CONTRIBUTING.md#code-style)
and [commit
standards](https://github.com/prestodb/presto/blob/master/CONTRIBUTING.md#commit-standards).
- [ ] PR description addresses the issue accurately and concisely. If
the change is non-trivial, a GitHub Issue is referenced.
- [ ] Documented new properties (with its default value), SQL syntax,
functions, or other functionality.
- [ ] If release notes are required, they follow the [release notes
guidelines](https://github.com/prestodb/presto/wiki/Release-Notes-Guidelines).
- [ ] Adequate tests were added if applicable.
- [ ] CI passed.

## Release Notes

```
== NO RELEASE NOTE ==
```
AnuragKDwivedi pushed a commit to AnuragKDwivedi/presto-1 that referenced this pull request Apr 21, 2025
@unidevel @AnuragKDwivedi
Add github action to publish artifacts for presto stable release (pre…
a6f0e81 
…stodb#24821)

## Description

This is a follow up of PR prestodb#24697,
seperate the github release actions into 2 PRs. This is the second one -
publish release artifacts like jars, docker images, websites, etc.

The document of stable release process can be found in
https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)

<!---Describe your changes in detail-->
Prior to the coming release, there were 5 steps:

- [Step 1 - Create a release branch and increment the version in the
master
branch](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)#step-1-create-a-release-branch-and-increment-the-version-in-the-master-branch)
- [Step 2 - Create release notes
PR](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months))
- [Step 3: clean up the
tag](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)#step-3-clean-up-the-tag)
- [Step 4: Publish Maven and Docker
artifacts](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)#step-4-publish-maven-and-docker-artifacts)
- [Step 5: Publish docs
website](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)#step-5-publish-docs-website)

### Action "Presto Stable Release -Publish"

<img width="969" alt="presto_release_publish_workflow"
src="https://github.com/user-attachments/assets/31e941ac-c3b9-4a2d-9660-1e9bfaaf2e26"
/>

- [Step 3: clean up the
tag](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)#step-3-clean-up-the-tag)
- [Step 4: Publish Maven and Docker
artifacts](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)#step-4-publish-maven-and-docker-artifacts)
- [Step 5: Publish docs
website](https://github.com/prestodb/presto/wiki/Stable-release-process-(every-2-months)#step-5-publish-docs-website)

#### Parameters

<img width="309" alt="presto_release_publish_inputs"
src="https://github.com/user-attachments/assets/54e18451-e99c-43b0-9921-a90983edd592"
/>


#### Jobs

![image](https://github.com/user-attachments/assets/4fafe966-92df-44df-a06a-b013fd5b806c)


This PR required
prestodb/presto-release-tools#47,
prestodb/prestodb.github.io#291 to be merged and
released a new version`presto-release-tools` of before using these 2
actions

## Motivation and Context

## Impact
Presto stable release

## Test Plan
- Tested with my env
- Publish => https://github.com/unix280/presto/actions/runs/13844025717
- Test with new release 0.292 after merged

## Contributor checklist

- [ ] Please make sure your submission complies with our [contributing
guide](https://github.com/prestodb/presto/blob/master/CONTRIBUTING.md),
in particular [code
style](https://github.com/prestodb/presto/blob/master/CONTRIBUTING.md#code-style)
and [commit
standards](https://github.com/prestodb/presto/blob/master/CONTRIBUTING.md#commit-standards).
- [ ] PR description addresses the issue accurately and concisely. If
the change is non-trivial, a GitHub Issue is referenced.
- [ ] Documented new properties (with its default value), SQL syntax,
functions, or other functionality.
- [ ] If release notes are required, they follow the [release notes
guidelines](https://github.com/prestodb/presto/wiki/Release-Notes-Guidelines).
- [ ] Adequate tests were added if applicable.
- [ ] CI passed.

## Release Notes

```
== NO RELEASE NOTE ==
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ZacBlanco ZacBlanco ZacBlanco approved these changes

@wanglinsong wanglinsong wanglinsong approved these changes

@alileclerc alileclerc Awaiting requested review from alileclerc

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@unidevel @ZacBlanco @wanglinsong