fixed date to 28th for community event blog

[rpallavisharma]

User description

Thanks for contributing to the Selenium site and documentation!
A PR well described will help maintainers to review and merge it quickly

Before submitting your PR, please check our contributing guidelines.
Avoid large PRs, and help reviewers by making them as simple and short as possible.

Description

the date in the community event blog was wrong, so fixed it.

Motivation and Context

change was required as blog had incorrect date earlier.

Types of changes

• Change to the site (I have double-checked the Netlify deployment, and my changes look good)
• Code example added (and I also added the example to all translated languages)
• Improved translation
• Added new translation (and I also added a notice to each document missing translation)

Checklist

• I have read the contributing document.
• I have used hugo to render the site/docs locally and I am sure it works.

---

PR Type

Bug fix

---

Description

• Corrected community event blog date from October 18th to 28th

---

Diagram Walkthrough

flowchart LR
  A["Blog Metadata"] -- "Update date field" --> B["2024-10-28"]
  C["Old Date: 2024-10-18"] -.-> B

Loading

File Walkthrough

	Relevant files
Bug fix	selenium-milestone-20yrs-blog.md Correct blog post publication date                                              website_and_docs/content/blog/2024/selenium-milestone-20yrs-blog.md Updated blog post date from 2024-10-18 to 2024-10-28 Corrects the publication date for the Selenium 20-year milestone celebration blog +1/-1

---

[netlify]

✅ Deploy Preview for selenium-dev ready!

Name	Link
🔨 Latest commit	c62a1a6
🔍 Latest deploy log	https://app.netlify.com/projects/selenium-dev/deploys/690236e4c4ffcf000862dbf6
😎 Deploy Preview	https://deploy-preview-2515--selenium-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[qodo-merge-pro]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-merge-pro]

PR Code Suggestions ✨

No code suggestions found for the PR.