Skip to content

fix: revert DEFAULT_SENTINEL for defaultValue#5123

Merged
daniel-kmiecik merged 1 commit intomasterfrom
revert-sentinel-default
Apr 10, 2026
Merged

fix: revert DEFAULT_SENTINEL for defaultValue#5123
daniel-kmiecik merged 1 commit intomasterfrom
revert-sentinel-default

Conversation

@daniel-kmiecik
Copy link
Copy Markdown
Collaborator

@daniel-kmiecik daniel-kmiecik commented Apr 10, 2026

Description

Reverting DEFAULT_SENTINEL for default value
Fixes: #5090 #5086

Type of Change

  • 🐛 Bug fix
  • ✨ New feature
  • ♻️ Refactor (non-breaking change)
  • 🧪 Tests
  • 📝 Documentation
  • 🧹 Chore (build or tooling)

Checklist

  • I have added/updated tests as needed
  • I have added/updated documentation where applicable
  • The PR title is descriptive
  • The code builds and passes tests locally
  • I have linked related issues (if any)

Screenshots / Additional Context

@daniel-kmiecik daniel-kmiecik merged commit 935d6c4 into master Apr 10, 2026
7 checks passed
@daniel-kmiecik daniel-kmiecik deleted the revert-sentinel-default branch April 10, 2026 14: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.

[Bug]: swagger-annotations 2.2.45 still emits spurious additionalProperties/contains/unevaluatedItems with "##default" sentinel on response schemas

2 participants