Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Update release instructions #5364

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

Merged
emilykl merged 2 commits into main from release-instructions-cleanup
Oct 3, 2025
Merged

Update release instructions #5364

emilykl merged 2 commits into main from release-instructions-cleanup
Oct 3, 2025

Conversation

@emilykl
Copy link
Contributor

@emilykl emilykl commented Oct 2, 2025

Clean up and improve release instructions.

These edits reflect the steps I followed for the most recent release (6.3.1).

@emilykl emilykl force-pushed the release-instructions-cleanup branch from 7957bed to 10c3321 Compare October 2, 2025 18:41
Copy link
Contributor

@camdecoster camdecoster Oct 3, 2025

Choose a reason for hiding this comment

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

I think we should maintain plotly.py and plotly.js to match what's shown in the repos. Was there something that prompted the change?

Copy link
Contributor Author

@emilykl emilykl Oct 3, 2025

Choose a reason for hiding this comment

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

What do you mean by "to match what's shown in the repos"?

I changed it because I think the capitals make it easier to read, but I could be convinced otherwise.

Copy link
Contributor

@camdecoster camdecoster Oct 3, 2025

Choose a reason for hiding this comment

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

I mean that we refer to the libraries as "plotly.xy" instead of "Plotly.xy" in the README for each repo. It's not a big deal, but I always try to use the proper name for an item. Like "GitHub" instead of "Github".

Copy link
Contributor Author

@emilykl emilykl Oct 3, 2025

Choose a reason for hiding this comment

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

Yeah fair enough, I guess we should keep lowercase unless/until we change the styling across the board.

RELEASE.md Outdated
Comment on lines 35 to 37
- `git add -u`
- `git commit -m "version changes for vX.Y.Z"`
- `git push`
Copy link
Contributor

@camdecoster camdecoster Oct 3, 2025

Choose a reason for hiding this comment

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

Suggested change
- `git add -u`
- `git commit -m "version changes for vX.Y.Z"`
- `git push`
```sh
git add -u
git commit -m "version changes for vX.Y.Z"
git push
```

emilykl reacted with thumbs up emoji
RELEASE.md Outdated
Comment on lines 40 to 41
- `git tag vX.Y.Z`
- `git push origin vX.Y.Z`
Copy link
Contributor

@camdecoster camdecoster Oct 3, 2025

Choose a reason for hiding this comment

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

FYI, the closing ``` isn't showing up in the suggestion for some reason.

Suggested change
- `git tag vX.Y.Z`
- `git push origin vX.Y.Z`
```sh
git tag vX.Y.Z
git push origin vX.Y.Z

emilykl reacted with thumbs up emoji

### Publishing to PyPI

The final step is to publish the release to PyPI. **You will need special permissions from Plotly leadership to do this.**.
Copy link
Contributor

@camdecoster camdecoster Oct 3, 2025

Choose a reason for hiding this comment

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

Could you add some context or add instructions for who to contact?

Copy link
Contributor Author

@emilykl emilykl Oct 3, 2025
edited
Loading

Choose a reason for hiding this comment

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

This doc is public so I'm not sure it makes sense to put more info here, but feel free to suggest different wording if you have an idea.

Copy link
Contributor

@camdecoster camdecoster Oct 3, 2025

Choose a reason for hiding this comment

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

Ah! Good point. Ignore this one.

emilykl reacted with thumbs up emoji
* Post an announcement to the [Plotly Python forum](https://community.plotly.com/c/plotly-python/5), with links to the README installation instructions and to the CHANGELOG.
* Update the previous announcement to point to this one
* Update the Github Release entry and CHANGELOG entry to have the nice title and a link to the announcement
* Update the GitHub Release entry and CHANGELOG entry to have the nice title and a link to the announcement
Copy link
Contributor

@camdecoster camdecoster Oct 3, 2025

Choose a reason for hiding this comment

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

👏

emilykl reacted with heart emoji
@emilykl emilykl merged commit bf29422 into main Oct 3, 2025
10 checks passed
emilykl added a commit that referenced this pull request Oct 9, 2025
Lowercase plotly.py and plotly.js in RELEASE.md (follow-up to #5364)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@camdecoster camdecoster camdecoster approved these changes

@LiamConnors LiamConnors Awaiting requested review from LiamConnors

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /