craftcms / craftcms/cms

Feature: Provide a system for sending security release notifications

Open
#3,591 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

security :lock:
Dominant language
PHP
Stars
3.6k
Forks
705
Avg merge
1d 5h
Merged PRs (30d)
134

Description

I am new to the Craft ecosystem and loving it so far. Now that my company has several sites live for clients, my mind has shifted to how we can best maintain these sites. My clients don't have a strong need to keep Craft and plugins up to date with the latest version, but I do think they'd value taking updates that include security fixes.

Coming from the world of Django, I am able to sign up for an email newsletter that sends me notifications releases, including security fixes. I know that other technical resources like Ubuntu have a similar methodology, and that would definitely solve my problem! Even if you did not want to go the way of sending an email newsletter, maybe there could be some sort of indicator in the updates section that easily brings security updates to the forefront.

For now, I have subscribed to receive alerts for all releases on the GitHub repo. In researching this topic, I've also gleaned some other reasonable solutions:

  • Install the Sherlock plugin

  • Follow Craft on Twitter — they mention any security fixes worth worrying about

The options above certainly do work, but it would be super helpful to get some sort of notification system or stream straight from Craft at some point in the future! Interested to know if this would be helpful for others as well.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are identified in the issue. Start by clarifying whether the intended outcome is email release notifications or an updates-page security indicator; done would mean a defined security-release notification system with an agreed delivery path.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
release, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.