Skip to content

Conversation

@Starefossen
Copy link
Member

Introduce new GraphQL issue types for Unleash release channels and implement corresponding resolvers. Enhance the issue checker to identify related issues and update the complexity calculation. Include functionality to parse major versions from release channel data and modify the fake Bifrost client for testing purposes.

@Starefossen Starefossen requested a review from a team as a code owner January 7, 2026 21:27
@Starefossen Starefossen force-pushed the unleash-outdated-warning branch from 12ac3af to 8c03c74 Compare January 7, 2026 21:44
MISSING_SBOM
VULNERABLE_IMAGE
UNLEASH_RELEASE_CHANNEL
UNLEASH_MISSING_RELEASE_CHANNEL
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I et tidligere issue så spurte jeg om denne skulle være påkrevd, men at det skulle være mulig å ende opp med en default.

Kan vi la være å introdusere en egen issue for det, og heller gjøre en av (med mindre det allerede er gjort)

  • gjøre feltet required
  • sette det på opprettelse til nåværende default kanal

og sette riktig channel for de som ble opprettet før det ble laget?

- Introduced UnleashReleaseChannelIssue and UnleashMissingReleaseChannelIssue types in GraphQL schema.
- Implemented corresponding resolvers for the new issue types.
- Enhanced complexity calculation for new fields in the GraphQL schema.
- Updated issue checker to identify and report issues related to Unleash release channels.
- Added functionality to parse major versions from release channel data.
- Modified fake Bifrost client to simulate release channels for testing.
- Updated resource and issue types to include Unleash-related issues.
@Starefossen Starefossen force-pushed the unleash-outdated-warning branch from 8c03c74 to 0aacc9a Compare January 9, 2026 08:36
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

Successfully merging this pull request may close these issues.

3 participants