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

Bump to 0.6.0 #511

Merged
merged 2 commits into from
Nov 21, 2022
Merged

Bump to 0.6.0 #511

merged 2 commits into from
Nov 21, 2022

Conversation

mkitti
Copy link
Member

@mkitti mkitti commented Nov 9, 2022

Should we be bumping to 0.6.0 or 0.6.0.dev?

cc: @MilesCranmer

@MilesCranmer
Copy link
Collaborator

Not sure. I don’t think 0.5.8 was actually released yet though.

@mkitti
Copy link
Member Author

mkitti commented Nov 9, 2022

Did you want to release a 0.5.8 from before your pull request?

@codecov
Copy link

codecov bot commented Nov 9, 2022

Codecov Report

Base: 87.34% // Head: 87.23% // Decreases project coverage by -0.11% ⚠️

Coverage data is based on head (a0f0e64) compared to base (b95e524).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #511      +/-   ##
==========================================
- Coverage   87.34%   87.23%   -0.12%     
==========================================
  Files          39       39              
  Lines        2316     2342      +26     
==========================================
+ Hits         2023     2043      +20     
- Misses        293      299       +6     
Impacted Files Coverage Δ
src/julia/release.py 100.00% <100.00%> (ø)
src/julia/options.py 92.12% <0.00%> (-4.07%) ⬇️
src/julia/tests/test_options.py 100.00% <0.00%> (ø)
src/julia/tests/test_juliaoptions.py 100.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

@MilesCranmer
Copy link
Collaborator

I think that’s a good idea. What’s the mechanism for doing a release?

@mkitti
Copy link
Member Author

mkitti commented Nov 9, 2022

I think that’s a good idea. What’s the mechanism for doing a release?

There seems to be a Github action setup to do that.

@MilesCranmer MilesCranmer self-requested a review November 13, 2022 23:56
@MilesCranmer
Copy link
Collaborator

I think we're ready to move to 0.6.0 (or at least, release 0.5.8), so packages can use the fixed optimize={}, threads={} to launch Julia. Want to create a release?

@mkitti
Copy link
Member Author

mkitti commented Nov 15, 2022

I will look at the release procedure this evening. The first target is Pypi, then conda-forge.

@mkitti
Copy link
Member Author

mkitti commented Nov 19, 2022

I'm going to work on this tomorrow.

@mkitti mkitti changed the title Bump to 0.6.0.dev Bump to 0.6.0 Nov 21, 2022
Copy link
Member Author

@mkitti mkitti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changing to 0.6.0 for release

ci/test-upload/tox.ini Outdated Show resolved Hide resolved
docs/source/conf.py Outdated Show resolved Hide resolved
src/julia/release.py Outdated Show resolved Hide resolved
Co-authored-by: Miles Cranmer <[email protected]>
@mkitti mkitti enabled auto-merge (squash) November 21, 2022 01:13
@mkitti mkitti merged commit 58842ab into JuliaPy:master Nov 21, 2022
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