fix: footer upgrade

[amolsontakke3576]

This pull request updates dependencies in the package.json file and adds a new packageManager field to specify the Yarn version being used.

Dependency updates:

• Updated @linuxfoundation/lfx-ui-core from version ^0.0.18 to ^0.0.19.

Package manager specification:

• Added a packageManager field to define the Yarn version as yarn@1.22.21+sha1.1959a18351b811cdeedbd484a8f86c3cc3bbaf72.

Summary by CodeRabbit

• Chores
  • Updated a core UI dependency to the latest version.

[coderabbitai]

Walkthrough

The dependency "@linuxfoundation/lfx-ui-core" in the package.json file was updated from version "^0.0.18" to "^0.0.19". No other files or configurations were modified in this change.

Changes

File(s)	Change Summary
package.json	Updated "@linuxfoundation/lfx-ui-core" version to "^0.0.19"

Possibly related PRs

• Feature: added cookies concent #49: Also updates the "@linuxfoundation/lfx-ui-core" dependency, indicating a related upgrade sequence.

Suggested reviewers

• mlehotskylf

Poem

A hop, a skip, a version bump,
The package hops with little thump.
From .18 to .19 we go,
The garden grows, dependencies flow.
With every change, a carrot earned—
Another lesson, neatly learned! 🥕

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between feb62f7 and eb3d5ae.

⛔ Files ignored due to path filters (1)

• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (1)

• package.json (1 hunks)

🔇 Additional comments (2)

package.json (2)

50-50: Dependency bump looks fine but double-check downstream breakage

@linuxfoundation/lfx-ui-core is moved from ^0.0.18 → ^0.0.19.
Patch-level bumps are normally safe, yet this package is still in the 0.x range, where SemVer does not guarantee stability. Please run the unit/E2E test suites and a quick manual smoke of the footer area before merging.

---

1-103: AI summary claims a packageManager field that is not in the file

The PR description and AI summary mention an added

"packageManager": "yarn@1.22.21+sha1.1959a18351b811cdeedbd484a8f86c3cc3bbaf72"

field, but it is absent from the actual package.json (lines 1-103).
Either the field was omitted in the commit or the summary is stale—please confirm.

Likely an incorrect or invalid review comment.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.