← 返回首页
Use _version.py that includes details using git by almarklein · Pull Request #784 · fastplotlib/fastplotlib · GitHub
Skip to content

Navigation Menu

Toggle navigation
Sign in
Appearance settings
Search or jump to...

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

Provide feedback

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

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
Resetting focus

Use _version.py that includes details using git#784

Merged
kushalkolar merged 1 commit into
mainfrom
versioning
Apr 1, 2025
Merged

Use _version.py that includes details using git#784
kushalkolar merged 1 commit into
mainfrom
versioning

Conversation

Copy link
Copy Markdown
Collaborator

Using the same module as pygfx and wgpu, which includes more detailed version info when you're inside a git repo.

Copy link
Copy Markdown

📚 Docs preview built and uploaded! https://www.fastplotlib.org/ver/versioning

Copy link
Copy Markdown
Member

So with this when it's a git version number, it's interpreated as version x.y.z + git-commit? So from now on bump right before release? I would usually bump after a release.

kushalkolar merged commit 8ef6581 into main Apr 1, 2025

Copy link
Copy Markdown
Collaborator Author

So with this when it's a git version number, it's interpreated as version x.y.z + git-commit?

Yes, e.g. my current pygfx is 0.7.0.post56+g092bc843.dirty, which is 56 commits after the last git vx.y.z tag, the git commit hash is also present. And the .dirty means that I have uncommitted changes :)

So from now on bump right before release? I would usually bump after a release.

Ah, so I guess that in your previous system the main is a bit like a preview (wip) of the upcoming release.

An advantage of bumping right before a release is that you can pick what number to bump, which usually depends a bit on how much (the API) has changed since the previous release.

I don't want to force either system on you. Actually, you could still bump after a release, and we could change the post to pre 🤷

Copy link
Copy Markdown
Member

Ah, so I guess that in your previous system the main is a bit like a preview (wip) of the upcoming release.

yup, let's just follow the same system for fpl after the next release, easier for everyone!

kushalkolar deleted the versioning branch April 18, 2025 07:24
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
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.

2 participants

Footer

© 2026 GitHub, Inc.