Prerelease v-9.2.1-pre-02 (#9618)

[msynk]

closes #9618

Summary by CodeRabbit

Release Notes: Version 9.2.1-pre-02

• Version Update

  • Updated version number from 9.2.1-pre-01 to 9.2.1-pre-02 across multiple projects and packages

• Package References

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

• Template Updates

  • Updated version comments for project templates
  • Refreshed boilerplate and project initialization scripts

• Scope

  • Consistent version increment across development tools, websites, and client-side libraries

[coderabbitai]

Walkthrough

This pull request involves a comprehensive version update across multiple projects and components from version 9.2.1-pre-01 to 9.2.1-pre-02. The changes primarily include updating version numbers in JavaScript/TypeScript scripts, project configuration files, package references, and version comments. The update spans various parts of the Bit framework ecosystem, including BlazorUI, Bswup, Bup, Butil, templates, and website projects.

Changes

File Path	Change Summary
Multiple JS/TS files	Version updated from 9.2.1-pre-01 to 9.2.1-pre-02 in version variables
.csproj files	Package references for Bit.CodeAnalyzers, Bit.SourceGenerators, and other Bit packages updated
Directory.Build.props	Template version comments updated
Directory.Packages.props	Multiple package versions incremented

Assessment against linked issues

Objective	Addressed	Explanation
Prerelease v-9.2.1-pre-02	✅

Poem

🐰 A version hop, a rabbit's delight,
From pre-01 to pre-02, taking flight!
Bits and bytes, now freshly dressed,
A code update, the bunny's quest! 🚀
Hop, skip, and version we go! 🌈

---

📜 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 4a4f795 and ae627a4.

📒 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 (30)

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

🔇 Additional comments (17)

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

13-20: LGTM! Version updates are properly implemented.

The package reference updates for Bit.CodeAnalyzers and Bit.SourceGenerators from 9.2.1-pre-01 to 9.2.1-pre-02 are correctly implemented with appropriate asset configurations. These development-time dependencies are part of the coordinated prerelease version update.

src/Bit.Build.props (1)

30-30: Version update looks good.
The version bump from 9.2.1-pre-01 to 9.2.1-pre-02 is consistent with the rest of the changes in this PR. No issues observed.

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

41-41: Command version update is correct.
This update from 9.2.1-pre-01 to 9.2.1-pre-02 is aligned with the global version changes. No concerns here.

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

4-11: Multiple package version updates.
These incremental version bumps look consistent with the global versioning in this release. No issues found.

---

49-49: Bit.Besql version bump.
The version alignment to 9.2.1-pre-02 reflects the rest of the PR changes. Looks good.

src/Templates/Boilerplate/Bit.Boilerplate/src/Directory.Packages.props (2)

4-11: Package version updates appear correct.
All these versions have been uniformly updated to 9.2.1-pre-02. Approved.

---

52-52: Bit.Besql version synchronization.
The version bump to match 9.2.1-pre-02 aligns with other files. No issues noted.

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

177-178: All good on the version update.
The .NET project template version is updated to 9.2.1-pre-02, which aligns with the rest of the repository. Looks good and consistent.

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

29-33: Ensure consistent usage of Bit analysis & generation libraries.
Both Bit.CodeAnalyzers and Bit.SourceGenerators are updated here to 9.2.1-pre-02. Confirm that all related logic or code transformations in the solution remain compatible with this new version.

✅ Verification successful

All projects consistently use version 9.2.1-pre-02 for both Bit.CodeAnalyzers and Bit.SourceGenerators

Based on the search results, all projects in the solution that reference Bit.CodeAnalyzers and Bit.SourceGenerators are using the same version (9.2.1-pre-02). This includes:

• All BlazorUI Demo projects
• Website projects (Platform, Sales, Careers)
• Template projects
• Directory.Packages.props and Directory.Packages8.props

The version is consistently maintained across the entire solution, ensuring compatibility.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search the entire project for references to Bit.CodeAnalyzers and Bit.SourceGenerators to confirm consistent usage
rg --heading --line-number "Bit.CodeAnalyzers|Bit.SourceGenerators"

Length of output: 12175

---

27-27: Keep references in sync.
The Bit.Bswup package reference version has been updated to 9.2.1-pre-02. Ensure other projects that rely on the same library also reference a compatible version to avoid mismatches.

✅ Verification successful

All package references to Bit.Bswup are in sync at version 9.2.1-pre-02

The search results show that all explicit version references to Bit.Bswup are consistently set to version 9.2.1-pre-02:

• In src/BlazorUI/Demo/Client/Bit.BlazorUI.Demo.Client.Web/Bit.BlazorUI.Demo.Client.Web.csproj: Version="9.2.1-pre-02"
• In src/Templates/Boilerplate/Bit.Boilerplate/src/Directory.Packages.props: Version="9.2.1-pre-02"
• In src/Templates/Boilerplate/Bit.Boilerplate/src/Directory.Packages8.props: Version="9.2.1-pre-02"

Other references to the package either:

1. Use the centrally managed version from Directory.Packages.props (e.g., <PackageReference Include="Bit.Bswup" /> without explicit version)
2. Are project references within the solution (using ProjectReference instead of PackageReference)
3. Are non-version related references (like script imports, using statements, etc.)

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Verify references to Bit.Bswup throughout the repo
rg --heading --line-number "Bit.Bswup"

Length of output: 11008

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

32-36: Consistent updates for tooling references.
The references for Bit.CodeAnalyzers and Bit.SourceGenerators were updated to 9.2.1-pre-02. This keeps the Windows project consistent with the rest of the solution.

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

29-33: Consistent usage of analyzers and source generators.
The references for Bit.CodeAnalyzers and Bit.SourceGenerators have been updated to 9.2.1-pre-02. This aligns with package versions across the repository, reducing any mismatch or dependency errors.

---

25-28: Validate version alignment for Blazor UI dependencies.
Bit.BlazorUI, Bit.BlazorUI.Icons, and Bit.BlazorUI.Assets references are upgraded to 9.2.1-pre-02. Make sure there are no cross-project dependencies on older versions that might cause conflicts.

✅ Verification successful

All Blazor UI dependencies are consistently using version 9.2.1-pre-02

Based on the search results, all references to Bit.BlazorUI, Bit.BlazorUI.Icons, and Bit.BlazorUI.Assets across the codebase are consistently using version 9.2.1-pre-02. This includes:

• Directory.Packages.props and Directory.Packages8.props in Templates/Boilerplate
• BlazorEmpty template project
• Platform, Sales, and Careers website projects

No version conflicts or mismatches were found.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Verify references to Bit.BlazorUI, Bit.BlazorUI.Icons, Bit.BlazorUI.Assets across the codebase
rg --heading --line-number "Bit.BlazorUI|Bit.BlazorUI.Icons|Bit.BlazorUI.Assets"

Length of output: 79427

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

25-35: Version updates look consistent!

The package references have been correctly updated to version 9.2.1-pre-02, maintaining consistent versioning across all Bit packages. The package configurations for analyzers and source generators are properly maintained.

Let's verify version consistency across the solution:

✅ Verification successful

Version consistency verified across the solution

All Bit package references across the solution are consistently using version 9.2.1-pre-02. This includes:

• Client projects (Careers, Sales, Platform)
• Server projects
• Shared libraries
• Templates
• Demo projects

The package configurations (PrivateAssets, IncludeAssets) are also properly maintained where required.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Verify version consistency across all .csproj files
echo "Checking for any inconsistent versions..."
rg "Include=\"Bit\." -A 1 "*.csproj" | grep -E 'Include="Bit\.|Version='

Length of output: 215

---

Script:

#!/bin/bash
# Search for .csproj files first, then check package versions
fd -e csproj -x sh -c 'echo "=== {} ==="; cat {} | grep -A 1 "Include=\"Bit\."'

Length of output: 14251

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

19-26: Version updates are properly aligned!

The analyzer and source generator package references have been correctly updated to version 9.2.1-pre-02, maintaining version consistency.

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

25-37: Version updates are complete and consistent!

All Bit package references have been correctly updated to version 9.2.1-pre-02, maintaining version consistency across the entire project. Package configurations and build settings are properly maintained.

Let's verify the build configurations are consistent:

✅ Verification successful

Build configurations are properly maintained!

The build configurations in Bit.Websites.Platform.Client.csproj are consistent with other similar client projects in the codebase. The project has the standard build tasks:

• BeforeBuildTasks (runs after CoreCompile)
• InstallNodejsDependencies
• BuildJavaScript
• BuildIsolatedScssFiles
• BuildGlobalScssFiles

These configurations match the build setup found in other client projects like Bit.Websites.Careers.Client and Bit.Websites.Sales.Client, ensuring consistent build behavior across the platform.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Verify build configurations across projects
echo "Checking build configurations..."
rg "BeforeBuildTasks" "*.csproj" -A 5

Length of output: 161

---

Script:

#!/bin/bash
# Let's try a different approach to find .csproj files first
echo "Finding .csproj files..."
fd -e csproj

# Then check for any build-related configurations
echo -e "\nChecking build configurations in all .csproj files..."
for proj in $(fd -e csproj); do
    echo "=== $proj ==="
    cat "$proj" | grep -A 5 "<.*Build.*>" || true
done

Length of output: 51519

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

88-95: LGTM! Version updates are consistent with the prerelease.

The package reference updates from 9.2.1-pre-01 to 9.2.1-pre-02 for both Bit.CodeAnalyzers and Bit.SourceGenerators align with the PR objectives.

Let's verify the version consistency across the solution:

✅ Verification successful

✅ Version consistency verified across all Bit. packages*

All Bit.* package references in the solution consistently use version 9.2.1-pre-02, including:

• Bit.CodeAnalyzers
• Bit.SourceGenerators
• Bit.BlazorUI
• Bit.BlazorUI.Icons
• Bit.BlazorUI.Assets
• Bit.Bswup
• Bit.Butil

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify version consistency across all .csproj files
# Expected: All Bit.* package references should use version 9.2.1-pre-02

echo "Checking Bit.* package versions in .csproj files..."
find . -name "*.csproj" -exec grep -A 3 'PackageReference Include="Bit\.' {} \;

Length of output: 11421

---

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.