Devicon icon naming stability across releases

Devicon is distributed as SVG and PNG assets under an MIT license for use in documentation, portfolios and developer tools. Icons are organized by technology categories with flat filenames that map to technology names and are typically referenced by filename via a package or CDN.

The set is maintained as a community repository where icons are added via contributions. There is no published deprecation or renaming policy for icons, so filenames can change between releases without a formal migration or compatibility notice.

For a project that needs consistent icon references over time, the decision point is how to treat filename stability as a design assumption when no formal stability commitment is documented.

Which documented stability guarantees, if any, exist for Devicon icon filenames and identifiers across releases? Does the project publish a deprecation or migration policy for renamed or removed icons? How should long-term consumers interpret version pinning in the absence of a formal naming stability commitment?