quarkusio / registry.quarkus.io

Quarkus Extension Registry application

https://registry.quarkus.io

quarkusio/registry.quarkus.io Issues

Review the default recommended stream list to take into account LTS versions
Closed 5 months ago
Maven Metadata Endpoint(s) returns 404
Closed 5 months ago1
Introduce a LTS column in the PlatformStream
Closed 8 months ago
Enable latency histogram
Closed a year ago5
Extension description is overridden by an older one
Updated a year ago
Auto-correct dead guides links caused by shifts in what 'latest' points to
Updated a year ago1
Using an invalid version as a target Quarkus version returns 204
Closed a year ago
Feature request: Endpoint to get the extensions, in a given stream
Updated a year ago2
Improve change auditing
Updated a year ago
Introduce contract tests
Updated a year ago
Support serving platform extension catalogs in addition to non-platform extension catalogs
Closed a year ago23
Allow pinning streams
Closed a year ago
More sophisticated "latest" identification in `extensions/all` to prefer final releases over more recent alphas
Updated 2 years ago1
/extensions/all endpoint dropping all metadata (including 'unlisted' field) for platform extensions
Closed 2 years ago4
Investigate how to support major platform releases and CRs for previous major releases
Closed 2 years ago1
Flyway fails when upgrading to 2.13.x
Closed 2 years ago
Registry client profiles
Updated 2 years ago2
Support Quarkus core version ranges in `ExtensionReleaseCompatibility`
Updated 2 years ago4
RC releases are preferred over Final releases
Closed 2 years ago
Store the artifact's SHA1 in the database
Updated 2 years ago
Native application fails with NoSuchMethodException when RestEasy Reactive is used
Closed 2 years ago1
`ArtifactParser` parses classifiers incorrectly
Closed 2 years ago1
Weird Strict-Transport-Security max-age value
Closed 2 years ago2
add recommended column for platform releases in registry
Closed 2 years ago
be able to explicitly set recommended version
Closed 2 years ago
`/client/platforms/all` does not order versions properly
Closed 2 years ago
registry.quarkus.redhat.com should promote the 2.7 stream once it's available in addition to 2.2
Closed 2 years ago4
API to list and search for all platform releases known to the registry
Closed 2 years ago5
Non-platform extensions JSON should at least match the requested quarkus core version
Closed 2 years ago
Support running on multiple replicas
Closed 3 years ago
Return 204 if no platforms were found
Closed 3 years ago
Limit the number of recommended streams to the latest two stable releases
Closed 3 years ago
Separate the notion of currently recommended platform versions for new projects from still supported versions
Closed 3 years ago4
Non-platform extension catalog IDs are wrong
Closed 3 years ago1
How to create a proxy in the Nexus version 3 repository
Closed 3 years ago2
Missing version in metadata.xml
Closed 3 years ago
Non-platform catalogs are missing the quarkus-core-version
Closed 3 years ago2
Create Nexus metadata artifacts
Closed 3 years ago
Create performance and load tests for registry.quarkus.io
Updated 3 years ago
Parameterize properties in the registry descriptor
Closed 3 years ago2
Platform extensions are listed in non-platform extension catalogs
Closed 3 years ago1
quarkus-platforms-1.0-SNAPSHOT-<quarkus-version>.json includes extra quarkus versions
Closed 3 years ago
Add artifacts with classifiers to the metadata.xml
Closed 3 years ago
Secure the database with separate users for admin and query operations
Updated 3 years ago1
Introduce a `quarkus-core-compatibility: unknown/compatible/incompatible` flag
Closed 3 years ago
Expose AdminEndpoint as a Kubernetes Operator
Closed 3 years ago1
Detecting latest Extension and Platform versions
Closed 3 years ago5
Allow scheduling checks for new versions of existing platforms and extensions
Closed 3 years ago8