Skip to content

chore(database): update module path for v2#151

Merged
intel352 merged 2 commits intomainfrom
chore/database-update-module-path-v2
Oct 31, 2025
Merged

chore(database): update module path for v2#151
intel352 merged 2 commits intomainfrom
chore/database-update-module-path-v2

Conversation

@github-actions
Copy link

Module Path Update for database v2.0.0

This PR updates the module path in `modules/database/go.mod` to include the `/v2` suffix as required by Go module versioning for major versions 2 and above.

Changes:

  • Module: database
  • Old module path: `github.com/CrisisTextLine/modular/modules/database`
  • New module path: `github.com/CrisisTextLine/modular/modules/database/v2`

Why This Change Is Needed:

According to Go module versioning requirements, when releasing a major version v2 or higher, the module path must include a version suffix. This ensures proper dependency resolution and prevents conflicts with v0/v1 versions.

Reference: https://go.dev/blog/v2-go-modules

Next Steps:

  1. Review and merge this PR
  2. After merging, re-run the module release workflow for database to complete the v2.0.0 release

This PR was automatically created by the module release workflow.

This updates the database module path from:
  github.com/CrisisTextLine/modular/modules/database
to:
  github.com/CrisisTextLine/modular/modules/database/v2

This is required for releasing version v2.0.0 according to Go module versioning requirements.
See https://go.dev/blog/v2-go-modules for more information.
require (
github.com/CrisisTextLine/modular v1.11.6
github.com/aws/aws-sdk-go-v2 v1.38.3
github.com/CrisisTextLine/modular/modules/database v1.4.0

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@copilot There should not be a reference to v1 database module from the v2 module. Why is this occurring?

Copy link

Copilot AI commented Oct 31, 2025

@intel352 I've opened a new pull request, #152, to work on those changes. Once the pull request is ready, I'll request review from you.

* Initial plan

* Plan to fix v1 database module reference in v2 module

Co-authored-by: intel352 <77607+intel352@users.noreply.github.com>

* fix: remove v1 database module reference from v2 module

Co-authored-by: intel352 <77607+intel352@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: intel352 <77607+intel352@users.noreply.github.com>
@github-actions
Copy link
Author

📋 API Contract Changes Summary

No breaking changes detected - only additions and non-breaking modifications

Changed Components:

Core Framework

Contract diff saved to artifacts/diffs/core.json

Module: auth

Contract diff saved to artifacts/diffs/auth.json

Module: cache

Contract diff saved to artifacts/diffs/cache.json

Module: chimux

Contract diff saved to artifacts/diffs/chimux.json

Module: database

Contract diff saved to artifacts/diffs/database.json

Module: eventbus

Contract diff saved to artifacts/diffs/eventbus.json

Module: eventlogger

Contract diff saved to artifacts/diffs/eventlogger.json

Module: httpclient

Contract diff saved to artifacts/diffs/httpclient.json

Module: httpserver

Contract diff saved to artifacts/diffs/httpserver.json

Module: jsonschema

Contract diff saved to artifacts/diffs/jsonschema.json

Module: letsencrypt

Contract diff saved to artifacts/diffs/letsencrypt.json

Module: logmasker

Contract diff saved to artifacts/diffs/logmasker.json

Module: reverseproxy

Contract diff saved to artifacts/diffs/reverseproxy.json

Module: scheduler

Contract diff saved to artifacts/diffs/scheduler.json

Artifacts

📁 Full contract diffs and JSON artifacts are available in the workflow artifacts.

@codecov
Copy link

codecov bot commented Oct 31, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 54.30%. Comparing base (70f033e) to head (ee7e8b4).
⚠️ Report is 1 commits behind head on main.

❗ There is a different number of reports uploaded between BASE (70f033e) and HEAD (ee7e8b4). Click for more details.

HEAD has 12 uploads less than BASE
Flag BASE (70f033e) HEAD (ee7e8b4)
auth 1 0
chimux 1 0
logmasker 1 0
jsonschema 1 0
eventlogger 1 0
letsencrypt 1 0
httpclient 1 0
scheduler 1 0
cache 1 0
httpserver 1 0
eventbus 1 0
reverseproxy 1 0
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #151      +/-   ##
==========================================
- Coverage   59.53%   54.30%   -5.24%     
==========================================
  Files          98       92       -6     
  Lines       20073    19384     -689     
==========================================
- Hits        11951    10527    -1424     
- Misses       6944     7703     +759     
+ Partials     1178     1154      -24     
Flag Coverage Δ
auth ?
bdd-auth 70.97% <ø> (ø)
bdd-cache 67.15% <ø> (ø)
bdd-chimux 73.80% <ø> (ø)
bdd-database 52.66% <ø> (+15.42%) ⬆️
bdd-eventbus 33.03% <ø> (ø)
bdd-eventlogger 61.60% <ø> (+0.26%) ⬆️
bdd-httpclient 40.98% <ø> (ø)
bdd-httpserver 62.29% <ø> (ø)
bdd-jsonschema 77.31% <ø> (ø)
bdd-letsencrypt 19.70% <ø> (ø)
bdd-logmasker 36.02% <ø> (ø)
bdd-reverseproxy 54.97% <ø> (ø)
bdd-scheduler 60.97% <ø> (ø)
cache ?
chimux ?
cli 47.27% <ø> (ø)
core-bdd 17.70% <ø> (ø)
database 57.61% <ø> (-3.33%) ⬇️
eventbus ?
eventlogger ?
httpclient ?
httpserver ?
jsonschema ?
letsencrypt ?
logmasker ?
merged-bdd 43.78% <ø> (+1.10%) ⬆️
reverseproxy ?
scheduler ?
total 57.11% <ø> (ø)
unit 64.16% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@intel352 intel352 merged commit dd953f3 into main Oct 31, 2025
47 of 48 checks passed
@intel352 intel352 deleted the chore/database-update-module-path-v2 branch October 31, 2025 19:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants