Skip to content

chore: bump outdated node.js packages to latest version #604

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

Merged
merged 5 commits into from
May 20, 2025

Conversation

Satyendra098
Copy link
Contributor

Description : This commit updates all Node.js dependencies to their latest compatible versions. It addresses potential security vulnerabilities, ensures compatibility with newer tooling, and brings in the latest features and fixes from upstream packages.

Key Updates :

1--Upgraded tailwindcss and related PostCSS packages to resolve nesting export issues.
2--Ensured Gatsby and plugin versions remain compatible after bump.
3--Regenerated package-lock.json to reflect new dependency tree.

Attached Screenshot :-

Screenshot from 2025-05-16 18-11-43

Screenshot from 2025-05-16 18-13-37

Copy link

netlify bot commented May 16, 2025

👷 Deploy Preview for cilium processing.

Name Link
🔨 Latest commit f1c0b26
🔍 Latest deploy log https://app.netlify.com/projects/cilium/deploys/6827332291e8550008306257

Copy link

netlify bot commented May 16, 2025

Deploy Preview for cilium ready!

Name Link
🔨 Latest commit 955196d
🔍 Latest deploy log https://app.netlify.com/projects/cilium/deploys/682b5faf37b9640007cc08ee
😎 Deploy Preview https://deploy-preview-604--cilium.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@Satyendra098 Satyendra098 changed the title chore chore: bump outdated node.js packages to latest version May 16, 2025
@xmulligan
Copy link
Member

Can you say if/how you followed this guide? https://github.com/cilium/cilium.io/blob/main/DEPENDENCY_UPDATES.md

@Satyendra098
Copy link
Contributor Author

I was updating the dependencies the wrong way , thanks for the help @xmulligan :)

@xmulligan
Copy link
Member

Is there a reason you removed package-lock.json?

@Satyendra098
Copy link
Contributor Author

@xmulligan No I have not remove package-lock.json

@xmulligan xmulligan merged commit 2aacea0 into cilium:main May 20, 2025
4 checks passed
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.

2 participants