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

Release notes for 1.6.0 #3631

Merged
merged 5 commits into from Apr 20, 2024
Merged

Release notes for 1.6.0 #3631

merged 5 commits into from Apr 20, 2024

Conversation

oprypin
Copy link
Contributor

@oprypin oprypin commented Apr 11, 2024

Preview: https://oprypin.github.io/mkdocs/about/release-notes/#version-160-2024-04-18

I still plan to do another stylistic pass over this, but for now these release notes are ready for anyone who wants to check these changes prior to the release.

PRs still remaining to be merged: https://github.com/mkdocs/mkdocs/milestone/18

@pawamoy
Copy link
Sponsor Contributor

pawamoy commented Apr 12, 2024

Thanks @oprypin, both the release notes and the upgraded mkdocs theme look good 👍

@oprypin oprypin added this to the 1.6.0 milestone Apr 17, 2024
@Andre601
Copy link
Contributor

I have to say, the dark mkdocs theme looks great. Really well done.

@oprypin oprypin marked this pull request as ready for review April 17, 2024 22:46
@tomchristie tomchristie requested review from pawamoy and a team April 18, 2024 14:32
@tomchristie
Copy link
Member

Thanks @oprypin.

Related to this PR... what's the current deploy process for mkdocs releases?

@oprypin
Copy link
Contributor Author

oprypin commented Apr 20, 2024

  1. Merge a PR that changes the version in __init__.py (this)
  2. Create and push a tag
  3. (GitHub Actions automatically pushes to PyPI)
  4. mkdocs gh-deploy
  5. Publish a "release" on GitHub, with copied release notes but they need to be manually edited so that links go to mkdocs.org

@oprypin oprypin merged commit 0998fec into master Apr 20, 2024
34 checks passed
@oprypin oprypin deleted the relnotes branch April 20, 2024 17:49
@squidfunk
Copy link
Sponsor Contributor

Thanks for all your hard work on MkDocs and all the best for your future!

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.

None yet

5 participants