Add hats outputs to lsdb feedstock#1916
Merged
h-vetinari merged 2 commits intoconda-forge:mainfrom Mar 7, 2026
Merged
Conversation
Contributor
Author
|
@conda-forge/core ready for review |
h-vetinari
approved these changes
Mar 7, 2026
Member
There was a problem hiding this comment.
The three separate conda-forge feedstocks has proven to be an operational headache for our team, and we'd like to manage all three builds via one feedstock and build cycle.
Xref conda-forge/lsdb-feedstock#83
once you've merged that PR, please open a PR here to archive the old feedstocks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See conda-forge/lsdb-feedstock#82
The three packages,
hats,lsdb, andhats-importare all maintained by my team, and currently via three separate feedstocks.lsdbandhats-importdepend on thehatspackage. All three packages are released (nearly) simultaneously via github and pypi, with the same release tag number (by convention).The three separate conda-forge feedstocks has proven to be an operational headache for our team, and we'd like to manage all three builds via one feedstock and build cycle.
Checklist: