Bump BCrypt.Net-Next from 4.0.3 to 4.1.0#613
Merged
barach6662001-bit merged 2 commits intomainfrom Apr 28, 2026
Merged
Conversation
--- updated-dependencies: - dependency-name: BCrypt.Net-Next dependency-version: 4.1.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
.NET
barach6662001-bit
added a commit
that referenced
this pull request
Apr 24, 2026
…#612) * feat(seasons): real Season entity replaces legacy year-list (PR #612) - Domain: Season (Code, Name, StartDate, EndDate, IsCurrent) : AuditableEntity - EF: unique (TenantId, Code), partial unique (TenantId, IsCurrent=true), CHECK (EndDate > StartDate), tenant soft-delete query filter - Migration AddSeasons + idempotent data seed (3 default seasons per tenant, Aug 1 -> Jul 31). DataSeeder backfills existing/test tenants at startup. - /api/seasons rewritten: List/GetCurrent/Create/Update/SetCurrent/Delete, CompanyAdmin or platform super-admin required for mutations. Delete blocks on linked CostRecord/Sale/AgroOperation within the season range; super-admin can force=true. - /api/admin/tenants/{id}/seasons/* for platform super-admin, audited via ISuperAdminAuditService. - Breaking frontend API change: getSeasons() returns SeasonDto[] (was number[]). Dashboard now navigates through real season records using StartDate/EndDate instead of synthesising Jan 1 - Dec 31 year windows from transaction timestamps. - 6 integration tests covering tenant isolation, SetCurrent flip semantics, delete safety rails, non-admin 403, and super-admin audit emission. * test(seasons): fix integration tests - seed MFA, ignore tenant filter in test scope * docs: promote PR #612 to Completed in ROADMAP, close TZ point 2 - ROADMAP.md: move PR #612 to Completed, promote PR #613 (Currency) to In progress - TZ.md: mark point 2 (Dashboard period switcher) fully CLOSED with PR #612 shipment notes
barach6662001-bit
added a commit
that referenced
this pull request
Apr 24, 2026
…ences (#623) * feat(currency): add ExchangeRate and UserPreferences entities + migration * feat(currency): NBU service, daily sync job, and currency API endpoints * feat(currency): frontend store, useFormatCurrency hook, Profile currency selector * test(currency): unit + integration tests for NBU service and currency endpoints - Unit tests for NbuCurrencyService (JSON parse, upsert, backfill, UAH short-circuit, cron next-run helper) - Integration tests for /api/currency/rates/latest, /api/currency/rates (business-day fallback, UAH=1), and /api/currency/preferences (valid/invalid) - Rewrite GetLatestRates query as per-code FirstOrDefault for reliable EF translation
This was referenced Apr 24, 2026
barach6662001-bit
added a commit
that referenced
this pull request
Apr 24, 2026
…to prevent data mislabelling (#631) PR #613 + #628 shipped a conversion layer that changes the currency LABEL but never multiplies by an exchange rate, so a value saved as 1000 UAH renders as '1000 USD' on the expenses page, which is a correctness bug and a potential data-integrity hazard once input-side conversion lands. Until the conversion layer is rebuilt: - Profile currency Select is disabled with a tooltip "Валютна конвертація в розробці, буде доступна найближчим часом". - On every currency-store `load()`, if the backend returned a preference other than UAH, we silently call updatePreferences('UAH') so stale USD/EUR settings do not keep mislabelling values on return visits. - setPreferredCurrency is hard-forced to UAH regardless of the argument, so any code path still invoking it cannot re-introduce a non-UAH state.
…ture/BCrypt.Net-Next-4.1.0
barach6662001-bit
deleted the
dependabot/nuget/src/AgroPlatform.Infrastructure/BCrypt.Net-Next-4.1.0
branch
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Updated BCrypt.Net-Next from 4.0.3 to 4.1.0.
Release notes
Sourced from BCrypt.Net-Next's releases.
4.1.0
What's Changed
New Contributors
Full Changelog: BcryptNet/bcrypt.net@4.0.3...v4.1.0
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)