Update changelog for DBLogger VARCHAR field size increase #65
Conversation
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
Co-authored-by: lmajano <137111+lmajano@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Update changelog with latest changes
Update changelog for DBLogger VARCHAR field size increase
Jan 14, 2026
Contributor
|
@copilot this is still missing the other changes before our previous release |
Contributor
Author
I can see the Unreleased section has two Fixed items that were there before my changes. Could you clarify which specific changes you'd like documented? Should I:
I want to make sure I capture all the right changes. |
There was a problem hiding this comment.
Pull request overview
This PR updates the changelog to document the DBLogger schema change that increased VARCHAR field sizes from their previous values to VARCHAR(1024) for URL-related fields.
Changes:
- Added a new entry under the "Changed" section in the Unreleased portion of the changelog
- Documents VARCHAR field size increase to 1024 for
host,path,queryString,referer, anduserAgentfields in the DBLogger table schema
| ### Fixed | ||
|
|
||
| - Allow for sub-modules to load AFTER cbsecurity loads. | ||
| - Make sure the jwt toke is not null when doing discovery in the JwtService. |
There was a problem hiding this comment.
Spelling error: "toke" should be "token".
Suggested change
| - Make sure the jwt toke is not null when doing discovery in the JwtService. | |
| - Make sure the jwt token is not null when doing discovery in the JwtService. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Reviewed commits since v3.6.0 and updated
changelog.mdto document the DBLogger schema change.Changes
DBLoggertable schemahost,path,queryString,referer, anduserAgentnow use VARCHAR(1024) to prevent data truncation for longer URLs and user agent stringsContext
The existing Unreleased section already contained two Fixed items. This update adds the schema change under the appropriate Changed category.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.