Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PrimeNG website out of sync #15616

Closed
rosenthalj opened this issue May 20, 2024 · 1 comment
Closed

PrimeNG website out of sync #15616

rosenthalj opened this issue May 20, 2024 · 1 comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@rosenthalj
Copy link
Contributor

Describe the bug

The current version of PrimeNG is 17.17.0. PrimeNG's website version is 17.16.1.
Also, when launching stackblitz from any PrimeNG example, package.json uses PrimeNG 17.16.1

The following video demonstrates the issue. Look at the PrimeNG version number on each of the pages.

PrimNGWebsiteOutofSync.mov

Environment

N/A

Reproducer

https://primeng.org/

Angular version

17

PrimeNG version

17.17.0

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

n/a

Browser(s)

all browsers

Steps to reproduce the behavior

  1. go to PrimNG website: https://primeng.org/ and check version number
  2. launch any stackblitz example and check package.json fo the primeng version number

Expected behavior

See the current primeNG version number: 17.17.0

@rosenthalj rosenthalj added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label May 20, 2024
@rosenthalj rosenthalj changed the title Component: TitlePrimNG website out of sync PrimeNG website out of sync May 20, 2024
@mehmetcetin01140
Copy link
Contributor

Hi, thanks for reporting the issue. The issue has been resolved, so I am closing it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
Projects
None yet
Development

No branches or pull requests

2 participants