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

amazonka-secretsmanager is not registered in stackage #978

Closed
ncaq opened this issue Feb 28, 2024 · 3 comments
Closed

amazonka-secretsmanager is not registered in stackage #978

ncaq opened this issue Feb 28, 2024 · 3 comments

Comments

@ncaq
Copy link

ncaq commented Feb 28, 2024

I see stackage/build-constraints.yaml at master · commercialhaskell/stackage,
amazonka-secretsmanager is not written to the stackage,
so extra-deps is required even in the latest stackage.

@endgame
Copy link
Collaborator

endgame commented Feb 28, 2024

Dupe of #969

@endgame endgame closed this as completed Feb 28, 2024
@ncaq
Copy link
Author

ncaq commented Feb 29, 2024

My apologies.
I thought you had simply forgotten to write it because it was not written, rather than commented out with a reason for blocking.

@endgame
Copy link
Collaborator

endgame commented Feb 29, 2024

No problem. I need to get a bunch of hackage bounds updated so that we clearly communicate that we're not yet GHC 9.8-ready, and then get enough stuff done that it's worth uploading ~300 packages to Hackage. Once that's done, I suppose that stackage will pick amazonka back up again.

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

No branches or pull requests

2 participants