Skip to content

fix(components)!: swap admonition caution and warning severity - #758

Merged
wesleyboar merged 1 commit into
mainfrom
fix/admonition-caution-warning-swap
Oct 7, 2026
Merged

wesleyboar merged 1 commit into
mainfrom
fix/admonition-caution-warning-swap

Conversation

@wesleyboar

@wesleyboar wesleyboar commented Oct 5, 2026 •

Copy link
Copy Markdown
Member

Overview

Swaps admonition caution and warning styling and demo use-case copy so severity matches typical interpretation.

Caution

Must update all clients, because this is a breaking change and I don't want to bump major version.

Related

required by:

Changes

  • fixed admonition caution vs warning message-type mapping and icon
  • updated admonition demo config.yml use cases
  • updated dist build output

Testing

  1. make start (or ensure Fractality is on port 3000 with this branch checked out).
  2. Open http://127.0.0.1:3000/components/detail/admonition
  3. Confirm Caution is red (error) and Warning is yellow (warning).

UI

Before After
Admonition caution and warning (before) Admonition caution and warning (after)

Caution and warning mapped to the wrong message types; align styles and demo copy with intended use.

Co-authored-by: Cursor <cursoragent@cursor.com>
@qodo-code-review

Copy link
Copy Markdown

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

@wesleyboar wesleyboar changed the title fix(components): swap admonition caution and warning severity fix(components)!: swap admonition caution and warning severity Oct 7, 2026
@wesleyboar
wesleyboar merged commit 594f24c into main Oct 7, 2026
@wesleyboar
wesleyboar deleted the fix/admonition-caution-warning-swap branch October 7, 2026 18:58
wesleyboar added a commit that referenced this pull request Oct 7, 2026
## Overview

Forces release-please to propose **2.59.0** (minor) instead of **3.0.0**
after `fix(components)!` on #758.

> [!IMPORTANT]
> **Why?** [v3 is a whole
project.](https://github.com/orgs/TACC/projects/10) I will update
clients to not break by immediately integrating this breaking change for
them.

## Related

- blocks merge of #759 until
this is on `main`
- required by TACC/mkdocs-tacc#43
- required by TACC/Core-CMS#1247

## Changes

- **added** empty commit with `Release-As: 2.59.0` footer (per
PUBLISHING.md)

## Testing

1. Merge this PR to `main`.
2. Confirm release-please updates
#759 to `chore(main): release
2.59.0` (not 3.0.0).

## Notes


Made with [Cursor](https://cursor.com)

Co-authored-by: Cursor <cursoragent@cursor.com>
wesleyboar added a commit that referenced this pull request Oct 7, 2026
PR Generated by `release-please`
---


##
[2.59.0](v2.58.4...v2.59.0)
(2026-10-07)


### ⚠ BREAKING CHANGES

* **components:** swap admonition caution and warning severity
([#758](#758))

> [!IMPORTANT]
> I carefully integrate into all clients to prevent breakage, to avoid
v3 release now.

### Bug Fixes

* **components:** swap admonition caution and warning severity
([#758](#758))
([594f24c](594f24c))


### Miscellaneous Chores

* force next release to v2.59.0 (Release-As footer)
([#761](#761))
([a952537](a952537))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
wesleyboar added a commit to TACC/Core-CMS that referenced this pull request Oct 7, 2026
## Overview

Reverts temporary mapping because Core-Styles fixed mapping.

## Related

requires:
- TACC/Core-Styles#758

## Changes

- **fixed** `extend.py` alert context mapping for warning
- **fixed** `admonition.cortal-icons.css` yellow alert icon target class
- **updated** `package-lock.json` for `@tacc/core-styles` 2.59.0

## Testing & UI

1. Have a running CMS instance with this branch.
2. Rebuild CSS.
3. Open http://127.0.0.1:8007/test/test-alert-style/.
4. Compare Admonition **warning** appearance to before.
5. Verify no change.

> [!IMPORTANT]
> No change expected.

| Before | After |
| - | - |
| <img width="920" alt="Bootstrap vs admonition warning row (before)"
src="https://github.com/user-attachments/assets/2206e491-38be-4515-a86a-f5abbaa0b7cd"
/> | <img width="920" alt="Bootstrap vs admonition warning row (after)"
src="https://github.com/user-attachments/assets/91f6c494-2586-4f95-80f3-6e69d8d6467e"
/> |

---------

Co-authored-by: Cursor <cursoragent@cursor.com>
wesleyboar added a commit to TACC/mkdocs-tacc that referenced this pull request Oct 7, 2026
## Overview

Aligns admonition caution/warning styling with Core-Styles and bumps the
theme CDN to **2.59.1**.

## Related

requires:
- TACC/Core-Styles#758
- https://github.com/TACC/Core-Styles/releases/tag/v2.59.1

required by:
- TACC/TACC-Docs#179
- DesignSafe-CI/DS-User-Guide#293

## Changes

- **swapped** `pymdownx.css` caution vs warning icons
- **updated** CDN pins for `core-styles.base.css` and
`core-styles.docs.css`
- **swapped** `extensions.md` caution vs warning usage
- **updated** theme version to **1.0.5**

## Testing

1. Start server using this branch.
2. Open `/extensions`.
3. Verify admonitions: **caution** red, **warning** yellow.
4. Verify: no other style changes.

## UI

| Before | After |
| - | - |
| <img width="757" alt="Admonition caution and warning (before)"
src="https://github.com/user-attachments/assets/e1d64e90-fc74-4b1b-ab55-d9bd2a736547"
/> | <img width="757" alt="Admonition caution and warning (after)"
src="https://github.com/user-attachments/assets/133be934-a6e6-4544-8ebc-1e2d2603f0d4"
/> |

---------

Co-authored-by: Cursor <cursoragent@cursor.com>
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.

1 participant