prismjs breaking changes

1.29.0

2 breaking changes, first published August 23, 2022.

• Behavior changed Line Highlight
  Highlight ranges outside the code's lines are now ignored and offsets are applied when clamping ranges, which can change the highlighted lines. github.com
• Behavior changed Normalize Whitespace
  The plugin gained configuration through attributes, so existing setups may now be read differently; review any whitespace settings you rely on. github.com

1.28.0

9 breaking changes, first published April 17, 2022.

• Renamed Ada
  The Ada token previously named attr-name is now called attribute, with attr-name kept as an alias. Update selectors that target the old name. github.com
• Renamed Flow
  The alias of the Flow type token is now class-name. Update styles or plugins that rely on the old alias. github.com
• Renamed GEDCOM
  The GEDCOM token previously called tag is now called record. Update code that targets the old token name. github.com
• Renamed NEON
  The alias of the NEON key token is now property. Update styles or plugins that rely on the old alias. github.com
• Renamed properties
  Token names are now key and value, with attr-name and attr-value kept only as aliases. Update any CSS or plugin code that targets the old token names. github.com
• Behavior changed AutoHotkey
  AutoHotkey tokens were changed to the standard token set. Update any code that targets its previous token names. github.com
• Behavior changed Excel Formula
  The function-name, range and cell tokens now use different aliases. Update any styling or plugin code that relies on the old aliases. github.com
• Behavior changed Keep Markup
  The plugin now passes original token nodes rather than clones. Code that mutates nodes it receives may see different results. github.com
• Behavior changed VHDL
  Attribute is now a distinct token instead of being tagged as keyword. Update styles that depended on the old tagging. github.com

Check your code

These are the changes. To see which of them reach your code, scan a public repository, or have your coding agent call check_code with your manifest or lockfile over MCP. The API reads every change in every version, not only the newest. On Team and up, a fix pull request opens for the changes that reach a connected repository. Nothing merges or deploys.