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

Gymnasium v1.0.0 alphas #33

Open
1 task done
pseudo-rnd-thoughts opened this issue Feb 21, 2024 · 4 comments
Open
1 task done

Gymnasium v1.0.0 alphas #33

pseudo-rnd-thoughts opened this issue Feb 21, 2024 · 4 comments
Labels
question Further information is requested

Comments

@pseudo-rnd-thoughts
Copy link
Contributor

Solution to issue cannot be found in the documentation.

  • I checked the documentation.

Issue

Conda-forge doesn't seem to have created an auto PR for the 1.0.0 alpha 1

Installed packages

.

Environment info

.
@pseudo-rnd-thoughts pseudo-rnd-thoughts added the bug Something isn't working label Feb 21, 2024
@traversaro
Copy link
Contributor

Indeed probably this is a bug in the version autotick bot, or somehow it detects it is an alpha version.
Anyhow, note that creating pre-release on conda-forge requires a bit more modifications beside bumping the version in the recipe: see https://conda-forge.org/docs/maintainer/knowledge_base/#pre-release-builds for more details.

@h-vetinari
Copy link
Member

The bot does not open PRs for pre-release versions, you'll need to open a PR manually. If you want to also release those builds (not just run the CI through its paces), the linked docs are the right place, but it's not very complicated. We'd just need to add:

channel_targets:
  - conda-forge gymnasium_dev  # or gymnasium_alpha or ...

to recipe/conda_build_config.yaml and then rerender. I can create a branch for this, so we don't do have to do these things on main, which is supposed to have the latest GA version.

@h-vetinari h-vetinari added question Further information is requested and removed bug Something isn't working labels Feb 21, 2024
@pseudo-rnd-thoughts
Copy link
Contributor Author

@h-vetinari With v0.29.1 merged, could we make a PR for v1.0.0a1.

I was intending this as a testing ground for alpha 1 as conda tests on windows (and mac) which we don't have on the main repo so I don't care if we don't end up merging until v1.0.0 is fully done

@traversaro
Copy link
Contributor

@h-vetinari With v0.29.1 merged, could we make a PR for v1.0.0a1.

I was intending this as a testing ground for alpha 1 as conda tests on windows (and mac) which we don't have on the main repo so I don't care if we don't end up merging until v1.0.0 is fully done

#36

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants