-
Notifications
You must be signed in to change notification settings - Fork 80
Issues: purescript/registry-dev
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Publish API erroring with spurious "unregistered dependencies" error
#692
opened Jun 25, 2024 by
cakekindel
Trim temp directory from path when reporting errors in source code
good first issue
Good for newcomers
#686
opened Jan 26, 2024 by
thomashoneyman
Verify repository exists before attempting to clone it
good first issue
Good for newcomers
help wanted
Extra attention is needed
#684
opened Jan 22, 2024 by
flip111
Proxy GitHub issue API calls to the registry server
beta
enhancement
Something that would be good to have but it's not a priority
#649
opened Aug 3, 2023 by
thomashoneyman
Don't fail publishing when registry repos are behind the upstream
alpha
bug
Something isn't working
help wanted
Extra attention is needed
#646
opened Aug 1, 2023 by
thomashoneyman
Roll back package uploads on metadata failure
alpha
bug
Something isn't working
help wanted
Extra attention is needed
#645
opened Aug 1, 2023 by
thomashoneyman
Determine a specific legacy date cutoff or require all packages to compile
alpha
#577
opened Jan 10, 2023 by
thomashoneyman
Proposal: Reimplement 'purs publish' in the registry
alpha
#525
opened Sep 29, 2022 by
thomashoneyman
Enumerate the supported actors and their interactions (sequence diagrams) with the registry
#341
opened Feb 9, 2022 by
afcondon
Specify location to store
metadata
for registry clients
discussion
#322
opened Feb 2, 2022 by
thomashoneyman
List package versions from the Bower registry which will not be in the PureScript registry
beta
CI:bower-import
#300
opened Jan 19, 2022 by
thomashoneyman
Suggestion: Include compiler ranges in package metadata
alpha
enhancement
Something that would be good to have but it's not a priority
#255
opened Oct 18, 2021 by
thomashoneyman
Create a visual diagram showing the relationships between the various components of the registry
#85
opened Oct 12, 2020 by
JordanMartinez
Create a visual flowchart of how package addition, unpublishing, and version changing occurs
#84
opened Oct 12, 2020 by
JordanMartinez
Previous Next
ProTip!
Exclude everything labeled
bug
with -label:bug.