-
Notifications
You must be signed in to change notification settings - Fork 2
fix: include moder_update_updater.exe in GitHub Release and enable deterministic builds #325
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: ModerRAS/TelegramSearchBot
Length of output: 1216
🏁 Script executed:
Repository: ModerRAS/TelegramSearchBot
Length of output: 883
🏁 Script executed:
Repository: ModerRAS/TelegramSearchBot
Length of output: 1061
Determinism flags missing from referenced projects — SHA512 comparison won't stabilize.
The PR objective is to make unchanged assemblies produce identical SHA512 hashes so
ComputeChangedFilesonly flags truly changed files. However, these flags are only added toTelegramSearchBot.csprojin a Release-specific PropertyGroup. The six referenced projects at lines 101–106 (TelegramSearchBot.Common,.Database,.LLM,.Search,.LLMAgent,.SubAgent) have noDeterministic,DeterministicSourcePaths, orContinuousIntegrationBuildsettings.Each non-deterministic dependency will have a varying PE timestamp and MVID per build, so its file hash will change every run and the cumulative package logic will keep flagging them as changed even when nothing changed. The fix needs to be applied to every project whose output ends up in the build — preferably by centralizing it in a
Directory.Build.propsat the repo root so all projects pick it up uniformly.Critical caveat:
DeterministicSourcePaths=truerequires SourceLink/source-control integration to avoid build failures. No SourceLink package is currently configured in any project. Either addMicrosoft.SourceLink.GitHub(or equivalent) to the projects, or setDeterministicSourcePaths=falsewhile keepingDeterministic=true.♻️ Suggested approach: centralize via Directory.Build.props
Create
Directory.Build.propsnext to the solution file:Then remove the duplicated block from
TelegramSearchBot.csproj:<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|AnyCPU'"> <AllowUnsafeBlocks>true</AllowUnsafeBlocks> - <Deterministic>true</Deterministic> - <DeterministicSourcePaths>true</DeterministicSourcePaths> - <ContinuousIntegrationBuild>true</ContinuousIntegrationBuild> </PropertyGroup>🤖 Prompt for AI Agents