Skip to content

Conversation

@stuartparmenter
Copy link

@stuartparmenter stuartparmenter commented Sep 29, 2025

Proposed change

Codenotary CAS appears to have been discontinued in 2023 and removed from the builder workflows then as well. Removing references to it from the docs so people don't waste their time.

Type of change

  • Document existing features within Home Assistant
  • Document new or changing features for which there is an existing pull request elsewhere
  • Spelling or grammatical corrections, or rewording for improved clarity
  • Changes to the backend of this documentation
  • Remove stale or deprecated documentation

Checklist

  • I have read and followed the documentation guidelines.
  • I have verified that my changes render correctly in the documentation.

Additional information

Summary by CodeRabbit

  • Documentation
    • Removed all references to Codenotary CAS from security guidance and recommendations.
    • Deleted codenotary-related configuration options from add-on configuration and extended build docs.
    • Updated examples and tables to exclude codenotary, codenotary.signer, and codenotary.base_image entries.
    • Removed the “Add-on is signed with CodeNotary” security rating and its note.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Sep 29, 2025

📝 Walkthrough

Walkthrough

Removed all Codenotary-related configuration and security documentation from add-on docs, including options and extended build arguments in configuration, the Codenotary CAS section and related bullet in security, and the "signed with CodeNotary" security rating in presentation. No new alternatives or functional changes were introduced.

Changes

Cohort / File(s) Summary
Docs: Configuration options cleanup
docs/add-ons/configuration.md
Deleted codenotary keys from options and build sections: removed top-level codenotary entry and removed codenotary, codenotary.signer, codenotary.base_image from build args / extended build options.
Docs: Security guidance update
docs/add-ons/security.md
Removed entire “Codenotary CAS” section and removed the bullet referencing signing images with Codenotary CAS from "Making a secure add-on".
Docs: Presentation/security rating cleanup
docs/add-ons/presentation.md
Removed the "Add-on is signed with CodeNotary" security rating entry and its adjacent note from the Ingress/Security table.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Pre-merge checks and finishing touches

✅ Passed checks (5 passed)
Check name Status Explanation
Title Check ✅ Passed The pull request title "Get rid of codenotary references from addon docs" clearly and accurately describes the main change in the changeset. The PR removes all Codenotary CAS references from three documentation files (configuration.md, security.md, and presentation.md), which is exactly what the title states. The title is concise, specific, and directly relates to the primary objective of the pull request.
Linked Issues Check ✅ Passed The code changes fully meet the requirements from linked issue #2026. The issue requested that if Codenotary CAS is no longer available, documentation should be updated to remove references to it. The PR removes all Codenotary CAS references from the add-on documentation across three files: configuration options, security guidelines, and presentation/rating information, which directly addresses the second objective listed in the issue.
Out of Scope Changes Check ✅ Passed All changes in this pull request are directly in scope and related to the linked issue #2026. The PR removes Codenotary CAS references from configuration options, security documentation, and presentation ratings across three documentation files. No unrelated changes, refactoring, or additional modifications outside the stated objective of removing deprecated Codenotary references are present in the changeset.
Description Check ✅ Passed The pull request description is complete and properly follows the template structure. It includes all required sections with meaningful content: the "Proposed change" section explains why Codenotary CAS references should be removed (discontinued in 2023), the "Type of change" correctly identifies this as removing stale documentation, the checklist items are properly marked, and the "Additional information" section provides both the related issue number (#2026) and a link to the builder PR that removed Codenotary from workflows.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 86826be and 4b1d313.

📒 Files selected for processing (3)
  • docs/add-ons/configuration.md (0 hunks)
  • docs/add-ons/presentation.md (0 hunks)
  • docs/add-ons/security.md (0 hunks)
💤 Files with no reviewable changes (3)
  • docs/add-ons/configuration.md
  • docs/add-ons/presentation.md
  • docs/add-ons/security.md
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
  • GitHub Check: Redirect rules - developers-home-assistant
  • GitHub Check: Header rules - developers-home-assistant
  • GitHub Check: Pages changed - developers-home-assistant

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Tip

🧪 Early access (models): enabled

We are currently testing Sonnet 4.5 code review models, which should lead to better review quality. However, this model may result in higher noise levels in the review comments. Please disable the early access features if the noise level causes any inconvenience.

Note:

  • Public repositories are always opted into early access features.
  • You can enable or disable early access features from the CodeRabbit UI or by updating the CodeRabbit configuration file.

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@CoMPaTech CoMPaTech left a comment

Choose a reason for hiding this comment

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

Good spot and discussion on discord

Comment on lines -275 to -277
| codenotary | no | Enable container signature with codenotary CAS.
| codenotary.signer | no | Owner signer E-Mail address for this image.
| codenotary.base_image | no | Verify the base container image. If you use our official images, use `notary@home-assistant.io`
Copy link
Member

Choose a reason for hiding this comment

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

Same :)

@home-assistant
Copy link

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

@home-assistant home-assistant bot marked this pull request as draft September 30, 2025 19:34
@CoMPaTech
Copy link
Contributor

@frenck see discord developers; he found it at home-assistant/builder#182

@frenck
Copy link
Member

frenck commented Sep 30, 2025

And the supervisor?

@stuartparmenter
Copy link
Author

stuartparmenter commented Sep 30, 2025

As far as I can tell, codenotary CAS (the product/offering/etc) is dead. There are various remains of it still scattered around in HA, but it was disabled home-assistant/supervisor#4217 (and that appears to still stands today).

@frenck
Copy link
Member

frenck commented Sep 30, 2025

Sure but the option right now is still valid.

If we clean up the docs, we need to make sure the codebase is cleaned up too.

Docs are a result of the codebase change and not the other way around.

@stuartparmenter
Copy link
Author

The code base changes have been made already such that the options don’t do anything leaving the docs as misleading at best given they encourage its use and it doesn’t actually do anything (I wasted a good bit of time trying to get things setup, create a codenotary account, etc only to realize nothing used the options as I went to test that it worked).

Should further cleanup be done to fully remove it from the supervisor, all the addons, etc? Absolutely. But given these changes were made in 2023 it seems reasonable to remove the docs while someone carefully removes the code without breaking validation

@frenck
Copy link
Member

frenck commented Oct 5, 2025

I get your point; however, the documentation reflects the current implementation state. Documentation changes results from upstream cleanup, not the other way around.

../Frenck

@stuartparmenter
Copy link
Author

The documentation doesn't reflect the current implementation state. If the documentation was left in and all of the descriptions were changed to "this doesn't do anything" then it would. Would that be a better short term solution in your mind?

@stuartparmenter
Copy link
Author

This feels like such a textbook example of "Don’t let the perfect be the enemy of the good"

I'm going to move on to other things. If someone wants to merge this go ahead. Hopefully other people don't waste their time because of bad documentation or trying to help fix things for others.

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.

add-ons docs talk about using Codenotary CAS, but that seems to be a dead service / proprietary product offering

3 participants