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.

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

Versioning #17

Open
jdeschamps opened this issue Nov 12, 2024 · 2 comments
Open

Versioning #17

jdeschamps opened this issue Nov 12, 2024 · 2 comments
Assignees
@jdeschamps
Labels
enhancement New feature or request

Comments

@jdeschamps
Copy link
Member

Currently the way the versioning is set up, the latest would point to a version that does not exist (e.g. if on 0.1.6, it would point 0.2), but the 0.2 would show up in the link of the latest version...

Pydantic uses a similar system where the name of the latest version is actually "dev" (https://docs.pydantic.dev/dev/) and is probably alises as dev.

We should have a look at how they do it and get some inspiration.
@jdeschamps jdeschamps self-assigned this Dec 6, 2024
@jdeschamps jdeschamps added the enhancement New feature or request label Dec 6, 2024
@jdeschamps
Copy link
Member Author

Pydantic might be doing things automatically: https://github.com/pydantic/pydantic/blob/main/.github/workflows/docs-update.yml

@jdeschamps
Copy link
Member Author

We might be able to trigger workflows from CAREamics to careamics.github.io: https://medium.com/hostspaceng/triggering-workflows-in-another-repository-with-github-actions-4f581f8e0ceb

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jdeschamps jdeschamps

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jdeschamps