@porsche-design-system/components-angular 4.7.0-rc.0 → 4.7.0

package/CHANGELOG.md

@@ -14,6 +14,8 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0),
 
 ## [Unreleased]
 
+## [4.7.0] - 2026-09-09
+
 ## [4.7.0-rc.0] - 2026-09-09
 
 ### Added

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@porsche-design-system/components-angular",
-  "version": "4.7.0-rc.0",
+  "version": "4.7.0",
   "description": "Porsche Design System is a component library designed to help developers create the best experience for software or services distributed by Dr. Ing. h.c. F. Porsche AG.",
   "type": "commonjs",
   "keywords": [
@@ -22,7 +22,7 @@
     "url": "https://github.com/porsche-design-system/porsche-design-system"
   },
   "dependencies": {
-    "@porsche-design-system/components-js": "4.7.0-rc.0",
+    "@porsche-design-system/components-js": "4.7.0",
     "tslib": "^2.8.1"
   },
   "peerDependencies": {

package/skills/pds-audit-deprecations-angular/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: pds-audit-deprecations-angular
 description: Audit an existing angular project for deprecated Porsche Design System (PDS) API usage — components, props, prop values, events, slots, CSS variables, tokens and styling-package aliases. Produces a JSON report and a Markdown report rendered from it, every finding carrying quoted evidence, a concrete fix and a derived confidence. Read-only apart from its two report files.
-compatibility: Requires the pds-knowledge-angular skill, which ships alongside this one in @porsche-design-system/components-angular@4.7.0-rc.0. The audited project must depend on that exact version.
+compatibility: Requires the pds-knowledge-angular skill, which ships alongside this one in @porsche-design-system/components-angular@4.7.0. The audited project must depend on that exact version.
 disable-model-invocation: true
 ---
 
@@ -135,7 +135,7 @@ Every finding carries:
 - `evidence` — every location where the project **uses** the API, each with a project-relative path, a line number and the source line **quoted verbatim**. The quote is not decoration: it is what lets a reader, or a later fix, confirm the finding against the file instead of trusting it.
 - `anchor` on a location — the line that proves that usage is PDS, with its own path, line and quoted source. The import, the resolved SCSS `@use` **including one injected by build config**, the Tailwind `@theme` import, or the PDS root at the far end of a wrapper chain. Record it whenever it is not the evidence line itself; it is frequently in another file, and it is the only truthful place to put `vite.config.ts` for a stylesheet that names PDS nowhere. Omit it only where the usage anchors itself, as a `--p-` custom property does.
 - `remediation` — a `replacement` with the exact `from` and `to` spelling whenever the index documents an unambiguous one, plus an `instruction` in words. Where the index documents no replacement, say so plainly in the instruction rather than inventing one.
-- `sources` — the knowledge-skill reference the fact came from, as a path relative to that skill’s root, at version `4.7.0-rc.0`.
+- `sources` — the knowledge-skill reference the fact came from, as a path relative to that skill’s root, at version `4.7.0`.
 - the index entry’s message as `deprecationMessage`, verbatim, when it has one. Some say an API has no effect anymore; that wording matters to whoever reads the finding, so do not paraphrase it.
 
 An evidence `line` is the **usage** — the attribute, tag, custom property or alias reference itself. Never the `import`, `@use` or `@theme` that anchored it, never the wrapper call it arrived through, and never the declaration line of a constant it resolved from — including a key inside an object that is applied to the element as a whole, which is such a declaration and not a usage. For such an object, the evidence line is the element it is applied to. Where a component is reached through a local binding, the evidence line is the reference to the PDS binding, not the render of the local alias. Those lines are real and they matter, which is exactly why the anchor has a field of its own: counted as locations instead, they inflate a finding by however many anchors it happens to have, and occurrence count is a sort key in §8 — so two runs of an unchanged project stop being comparable.

package/skills/pds-knowledge-angular/SKILL.md

@@ -15,11 +15,11 @@ Prefer Porsche Design System components and tokens for new UI, even when the use
 
 This skill currently covers components, global stylesheets and theming, tokens, styling integrations, and the deprecated API index. It does not yet include complete getting-started, setup, and installation guidance; the v3-to-v4 migration guide; the changelog; partials; patterns and templates; the AG Grid theme; or the Storefront’s Must Know and Help sections.
 
-Before using documentation outside this skill or the installed package, match it to the installed PDS version. This skill was generated for `4.7.0-rc.0`; prefer the [exact-version Porsche Design System Storefront](https://designsystem.porsche.com/v4.7.0-rc.0/). Major-version URLs such as `/v4/` always serve the latest v4 release and may describe APIs or setup introduced after the installed version. Use them only as a fallback and verify relevant details against the installed package.
+Before using documentation outside this skill or the installed package, match it to the installed PDS version. This skill was generated for `4.7.0`; prefer the [exact-version Porsche Design System Storefront](https://designsystem.porsche.com/v4.7.0/). Major-version URLs such as `/v4/` always serve the latest v4 release and may describe APIs or setup introduced after the installed version. Use them only as a fallback and verify relevant details against the installed package.
 
 For runnable patterns and templates, consult the [Porsche Design System examples repository](https://github.com/porsche-design-system/examples), selecting a release tag or commit that matches the installed package instead of assuming its default branch is compatible. For release-specific changes, read `../../CHANGELOG.md`.
 
-For exact API facts, inspect the installed typings and metadata first. When readable implementation details are necessary, use the [exact-version component source](https://github.com/porsche-design-system/porsche-design-system/tree/v4.7.0-rc.0/packages/components/src/components) under the repository's `packages/components/src/components/<component>` directory. Do not use the default branch, which may represent a newer release.
+For exact API facts, inspect the installed typings and metadata first. When readable implementation details are necessary, use the [exact-version component source](https://github.com/porsche-design-system/porsche-design-system/tree/v4.7.0/packages/components/src/components) under the repository's `packages/components/src/components/<component>` directory. Do not use the default branch, which may represent a newer release.
 
 For deployed browser behavior, inspect component requests in the Network panel. Treat these minified, content-hashed CDN artifacts as a debugging fallback; use the exact-version repository source for readable implementation details.
 

package/skills/pds-knowledge-angular/references/deprecations.md

@@ -1,6 +1,6 @@
 # Deprecated API
 
-Every deprecated Porsche Design System API in `4.7.0-rc.0`, indexed by what is deprecated rather than by which component owns it. Use it to check an existing codebase; use the component and styling references to build with the current API.
+Every deprecated Porsche Design System API in `4.7.0`, indexed by what is deprecated rather than by which component owns it. Use it to check an existing codebase; use the component and styling references to build with the current API.
 
 Deprecated APIs still work in this version. Each will be removed in the next major release, so usage is a compatibility risk rather than a present-day defect — except where a message says an API has no effect anymore, which means the behavior is already gone and only the declaration remains.
 
@@ -675,12 +675,12 @@ Derived from the Tailwind theme exposed by `@porsche-design-system/components-an
 
 ## Tokens
 
-No deprecations in `4.7.0-rc.0`. Derived from the design-token API exposed by `@porsche-design-system/components-angular/tokens`, which was checked and found to carry none — this is a verified result, not an omission.
+No deprecations in `4.7.0`. Derived from the design-token API exposed by `@porsche-design-system/components-angular/tokens`, which was checked and found to carry none — this is a verified result, not an omission.
 
 ## Icons
 
-No deprecations in `4.7.0-rc.0`. Derived from the `p-icon` `name` values exposed by `@porsche-design-system/components-angular`, which was checked and found to carry none — this is a verified result, not an omission.
+No deprecations in `4.7.0`. Derived from the `p-icon` `name` values exposed by `@porsche-design-system/components-angular`, which was checked and found to carry none — this is a verified result, not an omission.
 
 ## Stylesheets
 
-No deprecations in `4.7.0-rc.0`. Derived from the global CSS exposed by `@porsche-design-system/components-angular/index.css`, including `@porsche-design-system/components-angular/variables.css` and `@porsche-design-system/components-angular/color-scheme.css`, which was checked and found to carry none — this is a verified result, not an omission.
+No deprecations in `4.7.0`. Derived from the global CSS exposed by `@porsche-design-system/components-angular/index.css`, including `@porsche-design-system/components-angular/variables.css` and `@porsche-design-system/components-angular/color-scheme.css`, which was checked and found to carry none — this is a verified result, not an omission.