Skip to content

Conversation

@ppfeister
Copy link
Contributor

@ppfeister ppfeister commented Jul 9, 2024

Fixes #615

Is it possible to republish crates with a new build number (-1 -2) rather than a bump in patch number (x.x.1 x.x.2) that triggers notifications? Or overwrite prior builds? I know you can't on PyPI but haven't tried on crates[.]io. If this doesn't make its way into the crate until the next release I'll just continue to build from source for now, using my existing spec file.

@bee-san
Copy link
Owner

bee-san commented Jul 11, 2024

Hiii! Thanks for this!! Since we don't have a CLA that means the code is licensed under what people thought the license was when contributing.

Sooo I think I will put a post in my Discord letting contributors know and seeing if they have any issues with this, in case they thought it was MIT when writing code :)

Copy link
Owner

@bee-san bee-san left a comment

Choose a reason for hiding this comment

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

Okay, couldnt find anyone that disapproved :)

@bee-san bee-san merged commit 663a3df into bee-san:master Jul 26, 2024
@ppfeister ppfeister deleted the patch-1 branch July 26, 2024 19:26
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.

License discrepancy between crate and source

2 participants