Skip to content

docs: Fix misleading links in UPDATING.md#38947

Merged
hainenber merged 1 commit into
apache:masterfrom
torzsmokus:patch-1
Mar 31, 2026
Merged

docs: Fix misleading links in UPDATING.md#38947
hainenber merged 1 commit into
apache:masterfrom
torzsmokus:patch-1

Conversation

@torzsmokus
Copy link
Copy Markdown
Contributor

@torzsmokus torzsmokus commented Mar 30, 2026

User description

SUMMARY

Fixed misleading links (where the link text and target differ)

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

Check the links :)

ADDITIONAL INFORMATION

  • Has associated issue:
  • Required feature flags:
  • Changes UI
  • Includes DB Migration (follow approval process in SIP-59)
    • Migration is atomic, supports rollback & is backwards-compatible
    • Confirm DB migration upgrade and downgrade tested
    • Runtime estimates and downtime expectations provided
  • Introduces new feature or API
  • Removes existing feature or API

CodeAnt-AI Description

Fix incorrect references in the upgrading notes

What Changed

  • Corrected two broken references in UPDATING.md so the link text now points to the matching pull request
  • The upgrade notes now send readers to the intended change entries

Impact

✅ Correct upgrade references
✅ Fewer broken documentation links
✅ Easier changelog navigation

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

I suggest a test against misleading links (where the link text and target differ)
@bito-code-review
Copy link
Copy Markdown
Contributor

bito-code-review Bot commented Mar 30, 2026

Bito Automatic Review Skipped - Files Excluded

Bito didn't auto-review this change because all changed files are in the exclusion list for automatic reviews. No action is needed if you didn't intend for the agent to review it. Otherwise, to manually trigger a review, type /review in a comment and save.
You can change the excluded files settings here, or contact your Bito workspace admin at evan@preset.io.

@dosubot dosubot Bot added the doc Namespace | Anything related to documentation label Mar 30, 2026
@codeant-ai-for-open-source codeant-ai-for-open-source Bot added the size:XS This PR changes 0-9 lines, ignoring generated files label Mar 30, 2026
@hainenber
Copy link
Copy Markdown
Contributor

Thank you for the fix!

@hainenber hainenber merged commit b1474aa into apache:master Mar 31, 2026
66 of 68 checks passed
sfirke pushed a commit to sfirke/superset that referenced this pull request Mar 31, 2026
qfcwell pushed a commit to qfcwell/superset that referenced this pull request May 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

doc Namespace | Anything related to documentation size/XS size:XS This PR changes 0-9 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants