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

When is the next crates.io release? #37

Closed
vi opened this issue Nov 12, 2019 · 7 comments
Closed

When is the next crates.io release? #37

vi opened this issue Nov 12, 2019 · 7 comments

Comments

@vi
Copy link

vi commented Nov 12, 2019 •
edited
Loading

I see a number of commits here, but on crates.io the library is Last Updated: 3 years ago.

What is maintainership status of the library?
vi added a commit to vi/websocat that referenced this issue Dec 5, 2019
@vi
Workaround for unpublished anymap
b9f8f50 
chris-morgan/anymap#37
chris-morgan/anymap#30

The needed commit happened 2 years ago:

chris-morgan/anymap@0850f5e
@RobbieMcKinstry
Copy link

Hi @chris-morgan! Might I suggest, if this crate is "finished" and in maintainance mode, cutting a v1.0.0 release on crates.io?

@Veetaha
Copy link

Veetaha commented Aug 21, 2020

ping @chris-morgan

@ruabmbua
Copy link

ping @chris-morgan especially the unreleased commit 479d756 would be very helpful. Without it, there is some undefined behavior triggered by https://github.com/rust-analyzer/rust-analyzer unit tests.
The alignment of the byte array casted to *const u64 seems to sometimes be 2 bytes, instead of 8, which fails in ptr::copy_nonoverlapping.

This was referenced May 7, 2021
Merged
Closed
This was referenced May 8, 2021
Closed
Closed
Closed
Closed
Open
Open
Open
Open
Closed
Open
Open
@repi repi mentioned this issue May 9, 2021
Closed
@github-actions github-actions bot mentioned this issue Jul 5, 2021
Open
@github-actions github-actions bot mentioned this issue Jul 12, 2021
Closed
@github-actions github-actions bot mentioned this issue Sep 21, 2021
Open
@chris-morgan chris-morgan mentioned this issue Jan 24, 2022
Closed
@chris-morgan
Copy link
Owner

anymap 1.0.0-beta.1 published finally. Some fairly significant changes, more than I expected, though external mostly very straightforward. Let me know what you reckon. I’ll leave it for a week then publish 1.0.0 if nothing seems awry.

Now to go through and close almost all the issues as resolved!

@chris-morgan chris-morgan mentioned this issue Jan 25, 2022
Closed
@ruabmbua
Copy link

Thank you!

@github-actions github-actions bot mentioned this issue Apr 19, 2022
Open
@jszwedko
Copy link

Hi @chris-morgan ! Apologies to bother, just stumbling across this issue due to a reported security advisory (https://nvd.nist.gov/vuln/detail/CVE-2021-38187). Would it be reasonable to tag the beta as 1.0.0 now?

@github-actions github-actions bot mentioned this issue May 21, 2022
Open
@github-actions github-actions bot mentioned this issue Jun 2, 2022
Open
@davepacheco davepacheco mentioned this issue Jun 14, 2022
Closed
@pinkforest pinkforest mentioned this issue Aug 22, 2022
Closed
@ivmarkov ivmarkov mentioned this issue Oct 31, 2022
Closed
@github-actions github-actions bot mentioned this issue Aug 4, 2023
Open
@gigaroby gigaroby mentioned this issue Aug 22, 2023
Closed
@jelmer
Copy link

jelmer commented Oct 20, 2023

Hi @chris-morgan , any chance you could submit something similar to rustsec/advisory-db#1378 ?

@github-actions github-actions bot mentioned this issue Nov 18, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@jelmer @vi @jszwedko @chris-morgan @ruabmbua @RobbieMcKinstry @Veetaha