Versioning #122
katestange
started this conversation in
Ideas
Versioning
#122
Replies: 2 comments
-
Yes, we might. It's most important in the context of publishing a package on PyPI, which I don't particularly see for backscope, but explicit server versioning might still be useful for syncing between backscope and frontscope changes. Since it's unlikely we will act on this any time soon, we might want to move this issue to a Discussion. |
Beta Was this translation helpful? Give feedback.
0 replies
-
With the get_commit endpoint working, there doesn't seem to be a strong impetus for this at the moment, but I am certainly open to counterpoint. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
@gwhitney wrote in #75:
"Most python projects have a "pyproject.toml" file (see https://packaging.python.org/en/latest/tutorials/packaging-projects/) that specifies a current version number of the project. That's updated (manually) when a new release of the project is made. But I see that backscope has no such thing."
We might want to implement such a thing, and then have an endpoint to display it.
Beta Was this translation helpful? Give feedback.
All reactions