Skip to content

Document process for creating new releases - #36

Open
markdboyd wants to merge 2 commits into
mainfrom
document-release-process
Open

Document process for creating new releases#36
markdboyd wants to merge 2 commits into
mainfrom
document-release-process

Conversation

@markdboyd

Copy link
Copy Markdown
Contributor

Changes proposed in this pull request:

  • create document to outline process for creating new releases

Things to check

  • For any logging statements, is there any chance that they could be logging sensitive data?
  • Are log statements using a logging library with a logging level set? Setting a logging level means that log statements "below" that level will not be written to the output. For example, if the logging level is set to INFO and debugging statements are written with log.debug or similar, then they won't be written to the otput, which can prevent unintentional leaks of sensitive data.

Security considerations

None

@markdboyd
markdboyd requested a review from a team as a code owner September 4, 2026 21:23
@markdboyd markdboyd changed the title create document to outline process for creating new releases Document process for creating new releases Sep 4, 2026
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.

1 participant