deps: bump bitcoinui to 1.0.8

[reez]

Description

Notes to the reviewers

Changelog notice

Checklists

All Submissions:

• I've signed all my commits
• I have formatted my code with swift-format per .swift-format file

New Features:

• I've added tests for the new feature
• I've added docs for the new feature

Bugfixes:

• This pull request breaks the existing API
• I've added tests to reproduce the issue which are now passing
• I'm linking the issue being fixed by this PR

Summary by CodeRabbit

• New Features

  • Updated the BitcoinUI package dependency to a specific version (1.0.8) for improved stability and compatibility.

• Bug Fixes

  • Ensured consistent use of the BitcoinUI package version, reducing potential issues from branch updates.

[coderabbitai]

Walkthrough

The changes in this pull request involve the LDKNodeMonday.xcodeproj/project.pbxproj file, specifically updating the dependency for the BitcoinUI package. The reference has been changed from a branch-based (main) to an exact version specification (1.0.8). This ensures that the project consistently utilizes this specific version, avoiding potential instability from using the latest branch updates. The overall structure of the project file remains unchanged, with other dependencies retaining their previous configurations.

Changes

File Path	Change Summary
LDKNodeMonday.xcodeproj/project.pbxproj	Updated BitcoinUI package reference from branch main to version 1.0.8. Other dependencies remain unchanged.

Possibly related PRs

• spm: bitcoinui main #101: Changes the BitcoinUI package reference from an exact version to a branch reference, contrasting the main PR's update.
• spm: bitcoinui 1.0.6 #108: Updates the BitcoinUI package reference from the main branch to exact version 1.0.6, similar to the main PR's update to 1.0.8.
• spm: ldk-node 0.4.0 #130: Introduces version 0.4.0 of the ldk-node package, relevant to changes in package dependencies.
• spm: ldk-node 0.4.2 #134: Updates the ldk-node package version from 0.4.0 to 0.4.2, also related to package dependency changes.

🐇 In the garden, where the code does play,
A version fixed, keeps troubles at bay.
From main to 1.0.8, we hop with glee,
Stability found, as sweet as can be!
Dependencies tidy, no more to roam,
In our project, we’ve made a home! 🌼

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between cfd2212 and 5b48df9.

📒 Files selected for processing (1)

• LDKNodeMonday.xcodeproj/project.pbxproj (1 hunks)

🔇 Additional comments (1)

LDKNodeMonday.xcodeproj/project.pbxproj (1)

909-910: LGTM! Good practice using exact version specification.

Moving from branch-based to version-based dependency management is a good practice as it:

• Ensures build reproducibility
• Prevents unexpected breaking changes
• Aligns with how other dependencies are managed in the project

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 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.