Closed bbrewington closed 10 months ago
Have a look a #139, it says the others get bumped when RPF ask for it.
This may well be because AstroPiAstroPi use this and any major changes might alter the project at the time of year it is running.(ignoring any RPF Project documents that may also need a tweak)
SenseEmu may need a tweak too https://github.com/astro-pi/python-sense-emu (and Trinket?)
Got it. From here, I see two options to make sure that people in the future understand this... which one is preferable?
Or am I misunderstanding the issue linked above?
Thank you for making the table. I have aligned the version numbers everywhere (and released a new version for the new Astro Pi year), and requested a new release be prepared by RP OS.
The version numbers are now all aligned, so I will close this issue. Thanks!
Seeing some version discrepancies across sites, so figured this table view would be the best way to collapse it all. I'm assuming everything needs to match the latest version in GitHub releases
Also, I'm new here and don't see a CI .yml file or maintenance instructions in a Wiki - so pardon my ignorance with this question: Would it make sense to set up automation so that when there is a new release in GH repo, it publishes updates to PyPI & readthedocs? And if that was automated, it might help ensure everything matches for future releases
2. init.py has version 2.4.0 (link)
3. setup.py has version 2.4.0 (permalink)
2. Needs to be updated in github.com/raspberrypi --> sense-hat