Prerelease v-9.3.1-pre-04 (#9710)

[msynk]

closes #9710

Summary by CodeRabbit

Release Notes for Version 9.3.1-pre-04

• Version Update

  • Updated version number from 9.3.1-pre-03 to 9.3.1-pre-04 across multiple packages and components

• Package References

  • Updated versions for:
    • Bit.BlazorUI
    • Bit.CodeAnalyzers
    • Bit.SourceGenerators
    • Bit.Bswup
    • Bit.Butil
    • Bit.Besql

• Templates

  • Updated Bit Boilerplate project template installation instructions
  • Modified template generation comments

• Service Workers

  • Updated version comments in service worker files

Note: This release primarily consists of version number increments across various components and packages.

[coderabbitai]

Walkthrough

This pull request involves a comprehensive version update across multiple projects and files from version 9.3.1-pre-03 to 9.3.1-pre-04. The changes primarily include updating version numbers in JavaScript/TypeScript scripts, project configuration files, service worker files, and package references. The update appears to be a systematic version increment across the entire Bit framework ecosystem.

Changes

File Path	Change Summary
Multiple JS/TS scripts	Version updated from 9.3.1-pre-03 to 9.3.1-pre-04
Multiple .csproj files	Package references for Bit.CodeAnalyzers, Bit.SourceGenerators updated
Build and package props files	Version comments and package versions incremented
Service worker files	Version comments updated

Assessment against linked issues

Objective	Addressed	Explanation
Prerelease v-9.3.1-pre-04	✅

Poem

🐰 A version hop, a rabbit's delight,
From pre-03 to pre-04, taking flight!
Bits and bytes in synchronized dance,
Updating code with a playful glance.
Version bumped, the framework sings! 🚀

---

📜 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 f200dab and 6220aa8.

📒 Files selected for processing (43)

• src/Besql/Bit.Besql/wwwroot/bit-besql.js (1 hunks)
• src/Bit.Build.props (1 hunks)
• src/BlazorUI/Bit.BlazorUI/Scripts/general.ts (1 hunks)
• src/BlazorUI/Demo/Bit.BlazorUI.Demo.Server/Bit.BlazorUI.Demo.Server.csproj (1 hunks)
• src/BlazorUI/Demo/Bit.BlazorUI.Demo.Shared/Bit.BlazorUI.Demo.Shared.csproj (1 hunks)
• src/BlazorUI/Demo/Client/Bit.BlazorUI.Demo.Client.Core/Bit.BlazorUI.Demo.Client.Core.csproj (1 hunks)
• src/BlazorUI/Demo/Client/Bit.BlazorUI.Demo.Client.Maui/Bit.BlazorUI.Demo.Client.Maui.csproj (1 hunks)
• src/BlazorUI/Demo/Client/Bit.BlazorUI.Demo.Client.Web/Bit.BlazorUI.Demo.Client.Web.csproj (1 hunks)
• src/BlazorUI/Demo/Client/Bit.BlazorUI.Demo.Client.Web/wwwroot/service-worker.published.js (1 hunks)
• src/BlazorUI/Demo/Client/Bit.BlazorUI.Demo.Client.Windows/Bit.BlazorUI.Demo.Client.Windows.csproj (1 hunks)
• src/BlazorUI/Demo/Directory.Build.props (1 hunks)
• src/Bswup/Bit.Bswup.Demo/wwwroot/service-worker.js (1 hunks)
• src/Bswup/Bit.Bswup.Demo/wwwroot/service-worker.published.js (1 hunks)
• src/Bswup/Bit.Bswup.NewDemo/Bit.Bswup.NewDemo.Client/wwwroot/service-worker.js (1 hunks)
• src/Bswup/Bit.Bswup.NewDemo/Bit.Bswup.NewDemo.Client/wwwroot/service-worker.published.js (1 hunks)
• src/Bswup/Bit.Bswup/Scripts/bit-bswup.progress.ts (1 hunks)
• src/Bswup/Bit.Bswup/Scripts/bit-bswup.sw.ts (1 hunks)
• src/Bswup/Bit.Bswup/Scripts/bit-bswup.ts (1 hunks)
• src/Bswup/FullDemo/Client/wwwroot/service-worker.js (1 hunks)
• src/Bswup/FullDemo/Client/wwwroot/service-worker.published.js (1 hunks)
• src/Bup/Bit.Bup/Scripts/bit-bup.progress.ts (1 hunks)
• src/Bup/Bit.Bup/Scripts/bit-bup.ts (1 hunks)
• src/Butil/Bit.Butil/Scripts/butil.ts (1 hunks)
• src/Templates/BlazorEmpty/Bit.BlazorEmpty/BlazorEmpty.Client/BlazorEmpty.Client.csproj (2 hunks)
• src/Templates/BlazorEmpty/Bit.BlazorEmpty/BlazorEmpty/BlazorEmpty.csproj (2 hunks)
• src/Templates/Boilerplate/Bit.Boilerplate/src/Client/Boilerplate.Client.Web/wwwroot/service-worker.published.js (1 hunks)
• src/Templates/Boilerplate/Bit.Boilerplate/src/Directory.Build.props (1 hunks)
• src/Templates/Boilerplate/Bit.Boilerplate/src/Directory.Packages.props (2 hunks)
• src/Templates/Boilerplate/Bit.Boilerplate/src/Directory.Packages8.props (2 hunks)
• src/Websites/Careers/src/Bit.Websites.Careers.Client/Bit.Websites.Careers.Client.csproj (1 hunks)
• src/Websites/Careers/src/Bit.Websites.Careers.Server/Bit.Websites.Careers.Server.csproj (1 hunks)
• src/Websites/Careers/src/Bit.Websites.Careers.Shared/Bit.Websites.Careers.Shared.csproj (1 hunks)
• src/Websites/Careers/src/Directory.Build.props (1 hunks)
• src/Websites/Platform/src/Bit.Websites.Platform.Client/Bit.Websites.Platform.Client.csproj (1 hunks)
• src/Websites/Platform/src/Bit.Websites.Platform.Client/Pages/Templates/Templates03GettingStartedPage.razor (1 hunks)
• src/Websites/Platform/src/Bit.Websites.Platform.Client/Pages/Templates/Templates03GettingStartedPage.razor.cs (1 hunks)
• src/Websites/Platform/src/Bit.Websites.Platform.Server/Bit.Websites.Platform.Server.csproj (1 hunks)
• src/Websites/Platform/src/Bit.Websites.Platform.Shared/Bit.Websites.Platform.Shared.csproj (1 hunks)
• src/Websites/Platform/src/Directory.Build.props (1 hunks)
• src/Websites/Sales/src/Bit.Websites.Sales.Client/Bit.Websites.Sales.Client.csproj (1 hunks)
• src/Websites/Sales/src/Bit.Websites.Sales.Server/Bit.Websites.Sales.Server.csproj (1 hunks)
• src/Websites/Sales/src/Bit.Websites.Sales.Shared/Bit.Websites.Sales.Shared.csproj (1 hunks)
• src/Websites/Sales/src/Directory.Build.props (1 hunks)

✅ Files skipped from review due to trivial changes (31)

• src/Butil/Bit.Butil/Scripts/butil.ts
• src/Bswup/Bit.Bswup.Demo/wwwroot/service-worker.js
• src/Bup/Bit.Bup/Scripts/bit-bup.ts
• src/Websites/Platform/src/Directory.Build.props
• src/BlazorUI/Demo/Client/Bit.BlazorUI.Demo.Client.Web/wwwroot/service-worker.published.js
• src/Besql/Bit.Besql/wwwroot/bit-besql.js
• src/Templates/Boilerplate/Bit.Boilerplate/src/Directory.Build.props
• src/BlazorUI/Bit.BlazorUI/Scripts/general.ts
• src/Websites/Careers/src/Directory.Build.props
• src/Bswup/Bit.Bswup.NewDemo/Bit.Bswup.NewDemo.Client/wwwroot/service-worker.published.js
• src/Bswup/FullDemo/Client/wwwroot/service-worker.published.js
• src/Websites/Sales/src/Directory.Build.props
• src/Bswup/Bit.Bswup/Scripts/bit-bswup.ts
• src/Bswup/Bit.Bswup.NewDemo/Bit.Bswup.NewDemo.Client/wwwroot/service-worker.js
• src/BlazorUI/Demo/Directory.Build.props
• src/Bup/Bit.Bup/Scripts/bit-bup.progress.ts
• src/Bswup/Bit.Bswup.Demo/wwwroot/service-worker.published.js
• src/Bswup/Bit.Bswup/Scripts/bit-bswup.progress.ts
• src/Websites/Platform/src/Bit.Websites.Platform.Server/Bit.Websites.Platform.Server.csproj
• src/Templates/Boilerplate/Bit.Boilerplate/src/Client/Boilerplate.Client.Web/wwwroot/service-worker.published.js
• src/Bswup/Bit.Bswup/Scripts/bit-bswup.sw.ts
• src/Templates/BlazorEmpty/Bit.BlazorEmpty/BlazorEmpty.Client/BlazorEmpty.Client.csproj
• src/Bswup/FullDemo/Client/wwwroot/service-worker.js
• src/Websites/Platform/src/Bit.Websites.Platform.Shared/Bit.Websites.Platform.Shared.csproj
• src/Websites/Careers/src/Bit.Websites.Careers.Server/Bit.Websites.Careers.Server.csproj
• src/BlazorUI/Demo/Bit.BlazorUI.Demo.Shared/Bit.BlazorUI.Demo.Shared.csproj
• src/BlazorUI/Demo/Bit.BlazorUI.Demo.Server/Bit.BlazorUI.Demo.Server.csproj
• src/Websites/Careers/src/Bit.Websites.Careers.Shared/Bit.Websites.Careers.Shared.csproj
• src/Templates/BlazorEmpty/Bit.BlazorEmpty/BlazorEmpty/BlazorEmpty.csproj
• src/Websites/Sales/src/Bit.Websites.Sales.Shared/Bit.Websites.Sales.Shared.csproj
• src/Templates/Boilerplate/Bit.Boilerplate/src/Directory.Packages.props

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: build and test for release

🔇 Additional comments (12)

src/Bit.Build.props (1)

30-30: LGTM! Version update is consistent with PR objective.

The version update from 9.3.1-pre-03 to 9.3.1-pre-04 in the central build properties file is correct.

src/Websites/Platform/src/Bit.Websites.Platform.Client/Pages/Templates/Templates03GettingStartedPage.razor.cs (1)

41-41: LGTM! Template installation command updated correctly.

The version update in the Bit.Boilerplate installation command is consistent with the central version.

src/Templates/Boilerplate/Bit.Boilerplate/src/Directory.Packages8.props (1)

4-11: LGTM! Package versions updated consistently.

All Bit package references have been correctly updated to version 9.3.1-pre-04, maintaining consistency across the project.

Also applies to: 50-50

src/Websites/Platform/src/Bit.Websites.Platform.Client/Pages/Templates/Templates03GettingStartedPage.razor (1)

177-178: LGTM! Documentation updated with correct version.

Both the NuGet package link and installation command have been updated to reflect the new version 9.3.1-pre-04.

src/Websites/Sales/src/Bit.Websites.Sales.Server/Bit.Websites.Sales.Server.csproj (1)

13-17: Version updates look consistent.

Package versions for Bit.CodeAnalyzers and Bit.SourceGenerators have been properly synchronized to 9.3.1-pre-04.

Also applies to: 17-21

src/BlazorUI/Demo/Client/Bit.BlazorUI.Demo.Client.Web/Bit.BlazorUI.Demo.Client.Web.csproj (1)

27-27: Version updates look consistent.

All Bit packages (Bit.Bswup, Bit.CodeAnalyzers, and Bit.SourceGenerators) have been properly synchronized to 9.3.1-pre-04.

Also applies to: 29-33, 33-37

src/BlazorUI/Demo/Client/Bit.BlazorUI.Demo.Client.Windows/Bit.BlazorUI.Demo.Client.Windows.csproj (1)

32-36: Version updates look consistent.

Package versions for Bit.CodeAnalyzers and Bit.SourceGenerators have been properly synchronized to 9.3.1-pre-04.

Also applies to: 36-40

src/Websites/Sales/src/Bit.Websites.Sales.Client/Bit.Websites.Sales.Client.csproj (1)

25-28: Version updates look consistent.

All Bit packages have been properly synchronized to 9.3.1-pre-04:

• Bit.BlazorUI and related packages (Icons, Assets)
• Bit.CodeAnalyzers
• Bit.SourceGenerators

Also applies to: 29-33, 33-37

src/Websites/Careers/src/Bit.Websites.Careers.Client/Bit.Websites.Careers.Client.csproj (1)

25-28: Version updates look consistent.

All Bit packages have been properly synchronized to 9.3.1-pre-04:

• Bit.BlazorUI and related packages (Icons, Assets)
• Bit.CodeAnalyzers
• Bit.SourceGenerators

Also applies to: 29-33, 33-37

src/BlazorUI/Demo/Client/Bit.BlazorUI.Demo.Client.Core/Bit.BlazorUI.Demo.Client.Core.csproj (1)

19-26: LGTM! Package versions are consistent with the prerelease update.

The version updates for Bit.CodeAnalyzers and Bit.SourceGenerators align with the PR's version increment to 9.3.1-pre-04.

Let's verify that all Bit package references are updated consistently:

✅ Verification successful

✅ All Bit package versions are consistently updated to 9.3.1-pre-04

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for any remaining Bit package references with the old version
rg "Include=\"Bit\.[^\"]+\" Version=\"9\.3\.1-pre-03\"" -l

Length of output: 55

---

Script:

#!/bin/bash
# Search for all Bit package references with surrounding context
rg "Include=\"Bit\." -A 2 "*.csproj"

Length of output: 86

---

Script:

#!/bin/bash
# Find all .csproj files and search for Bit package references
fd -e csproj -x rg "Include=\"Bit\." -A 2 {}

Length of output: 14376

src/Websites/Platform/src/Bit.Websites.Platform.Client/Bit.Websites.Platform.Client.csproj (1)

25-37: LGTM! Package versions are consistently updated.

All Bit package references have been updated to version 9.3.1-pre-04, maintaining consistency across the project.

Let's verify the BlazorUI.Icons WASM file compatibility with the new version:

src/BlazorUI/Demo/Client/Bit.BlazorUI.Demo.Client.Maui/Bit.BlazorUI.Demo.Client.Maui.csproj (1)

88-96: LGTM! Package versions are aligned with the prerelease update.

The version updates for Bit.CodeAnalyzers and Bit.SourceGenerators maintain consistency with other project files.

Let's verify that the package updates are compatible across all target frameworks:

✅ Verification successful

✅ Package updates are compatible with all target frameworks

The updated packages Bit.CodeAnalyzers and Bit.SourceGenerators are build-time only dependencies targeting netstandard2.0, ensuring compatibility with all MAUI target frameworks (android/ios/maccatalyst/windows).

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if the packages are available for all target frameworks
for framework in net9.0-android net9.0-ios net9.0-maccatalyst net9.0-windows10.0.19041.0; do
  echo "Checking packages for $framework"
  dotnet restore -r $framework
done

Length of output: 1259

---

Script:

#!/bin/bash
# Find all .csproj files and check their package references and target frameworks
fd -e csproj -x sh -c '
  echo "\nFile: {}"
  echo "=== Package References ==="
  grep -A 2 "PackageReference.*Bit\." "{}"
  echo "\n=== Target Frameworks ==="
  grep -A 2 "TargetFramework" "{}"
'

Length of output: 34728

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.