Upgrade to Astro 5.1.1 and Upgrade Yarn off 1.x to 4.x

[Husky-Devel]

This pull request includes several updates to the project configuration and dependencies, as well as a minor content addition to a component. The most important changes involve updating the package manager configuration, modifying the Dockerfile to support the new package manager, and updating dependencies in the package.json file.

Package Manager Configuration:

• Removed .yarnrc file and added nodeLinker: node-modules to .yarnrc.yml to switch to the node-modules linker. [1] [2]

Dockerfile Updates:

• Updated the Dockerfile to enable corepack, set the yarn version to berry, and use the new package manager configuration.

Dependency Updates:

• Updated various @astrojs dependencies to their latest versions in package.json.
• Updated astro dependency to version 5.1.1 in package.json.
• Added packageManager: "[email protected]" to package.json.

Content Update:

• Added a placeholder event for the year 2025 in the TimelineSkills.astro component.

[socket-security]

Report too large to display inline

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Possible typosquat attack	npm/[email protected]	Did you mean: emoji-regex~~-xs~~	yarn.lock	⚠︎
License Policy Violation	npm/[email protected]	License: AGPL-3.0-or-later - Not allowed by license policy (npm metadata, package/package.json) License: AGPL-3.0 - Not allowed by license policy (package/LICENSE.md)	yarn.lock	⚠︎
License Policy Violation	npm/[email protected]	License: CC-BY-4.0 - Not allowed by license policy (npm metadata, package/LICENSE, package/package.json)	yarn.lock	⚠︎

View full report↗︎

Next steps

What is a typosquat?

Package name is similar to other popular packages and may not be the package you want.

Use care when consuming similarly named packages and ensure that you did not intend to consume a different package. Malicious packages often publish using similar names as existing popular packages.

What is a license policy violation?

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]