v0.1.2: Security Patch for `tough-cookie` Vulnerability and Dependency Updates

We are delighted to introduce version v0.1.2 of the King's Temple Church website. This patch focuses primarily on addressing a critical security vulnerability and performing necessary updates to our dependencies.

Major Enhancements

1. Security Patch for tough-cookie Vulnerability #17
   • Addressed a Prototype Pollution vulnerability in the tough-cookie package by updating it to the secure version (4.1.3), and updated the razorpay dependency to maintain compatibility.
2. Update razorpay Dependency #16
   • Updated the razorpay package to a newer version compatible with the patched tough-cookie version, ensuring our payment gateway maintains top-notch security.
3. Github Actions Enhancements #15
   • Continued enhancements of our Github Actions setup, introducing more comprehensive workflows and refining the existing ones.

Code Snippets

As usual, due to the sensitive nature of these changes, specific code snippets are not included in these public release notes for security reasons.

Highlights of Changes

• A critical Prototype Pollution vulnerability in the tough-cookie package was addressed, enhancing the security of our site.
• The razorpay dependency was updated to ensure compatibility with the secure tough-cookie version, maintaining the high-security standards of our payment gateway.
• Further improvements were made to our Github Actions workflows, making our development and integration processes more robust.

Summary

This release mainly focuses on enhancing security by patching a critical vulnerability and updating dependencies. It also includes improvements to our Github Actions setup, making it more comprehensive and effective. We're confident that these changes will significantly improve the safety, reliability, and user experience of the King's Temple Church website.

Next Steps

Moving forward, we plan to continue enhancing our security measures, refining our development processes, and making improvements to our website's functionality. We will also extend our Github Actions workflows to cover more aspects of our development process, and keep optimizing our

Contributions

We extend our heartfelt thanks to the contributors to this release, especially @vamsii777, @prathamesh-dukare, @zeel-codder, and @Prachi-Jamdade.

Razorpay Integration and CI Fixes: Patch v0.1.1

We're excited to announce version v0.1.1 of the King's Temple Church website. This patch introduces important updates focusing on enhancing our payment systems and improving our continuous integration setup.

Major Enhancements

1. Razorpay Payment Gateway Integration #5
   • Implemented secure server-side fetching for Razorpay button id, enhancing payment security and simplifying button id
2. Github Actions Fixes #8
   • Fixed an issue with the Next.js 'app' directory in our Github Actions setup.
3. Payment Page Updates #7
   • Made various amount and UI fixes on the payment page to improve user experience.

Code Snippets

Due to the sensitive nature of the changes, the specific code snippets aren't included in this public release note for security reasons.

Highlights of Changes

• Razorpay Payment Gateway was integrated into the website to enhance payment security and simplify button id.
• An issue with the Next.js 'app' directory in our Github Actions setup was fixed to improve our continuous integration process.
• Various amount and UI fixes were made on the payment page to provide a smoother user experience.

Summary

This release brings significant improvements to our payment systems and continuous integration processes. It also includes various UI enhancements to provide a better user experience on the payment page. We're excited about the positive impacts these changes will have on our development workflow and user experience of the King's Temple Church website.

Next Steps

Looking ahead, we will continue to refine our development processes, improve our website's functionality, and introduce more enhancements to our payment systems. We're also planning to expand our Github Actions workflows to cover other aspects of our development process, and continue to optimize our code for efficient deployment and runtime performance.

We appreciate the support and contributions from all members of the development team, especially @vamsii777, @prathamesh-dukare, @zeel-codder, @Prachi-Jamdade for their contributions in this release. We're looking forward to the continued progress in our future updates.

Release v0.1.0

We are pleased to announce the release of version 0.1.0 for the King's Temple Church website. This release incorporates significant updates aimed at enhancing the deployment, documentation, and continuous integration processes of the project.

Major Enhancements

1. App Start Command Modification (#1, commit 3dc3419):

   • We have refined the start command in our package.json to be better suited for deployment on the App Platform. The command now specifically designates the host and port, reducing possible configuration errors during deployment.
   • The updated start command: "start": "next start -H 0.0.0.0 -p ${PORT:-8080}"

2. Documentation and Licensing Update (#2, commit 1a9a96f):

   • The README file has been thoroughly revised to offer a more comprehensive and precise overview of the project, its structure, and its deployment procedures.
   • A LICENSE file has been added to the repository, licensing the project under the MIT License. This license permits extensive use while retaining the necessary legal protections for our contributors.

3. Integration of GitHub Actions workflows (#3, commit f9c3ce7):

   • A new GitHub Actions workflow for our Node.js application has been introduced. This workflow is triggered on every push or pull request event on the 'main' branch, facilitating continuous integration and early issue detection.
   • The nextjs.yml workflow has been specifically tailored for the website, providing customized, effective CI for our Next.js application.

Code Snippet

The updated package.json:

{
  "name": "website",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start -H 0.0.0.0 -p ${PORT:-8080}"
  }
}

Highlights of Changes

• The start command in the package.json file was updated to ensure it's optimally configured for deployment on the App Platform. This includes specifying the host and port that the Next.js application should listen on.

• Our README file has been revamped with more comprehensive information about the project, including its purpose, technology stack, hosting environment, and project directory structure.

• We've added a LICENSE file to the repository, indicating that the project is now licensed under the MIT License. This license allows for wide-ranging use and reusability of the project while providing necessary legal protections for the contributors.

• A new GitHub Actions workflow was introduced for the Node.js application to streamline the development process. The workflow is triggered on every push or pull request event on the 'main' branch. This aims to catch issues early in the development cycle, improving the quality of the code and efficiency of the development process.

Summary

This release represents significant strides in improving the efficiency of our development process and the clarity of our project documentation. It also lays the groundwork for further enhancements and features in the future. We look forward to the positive impact these changes will have on our development workflow and the user experience of the King's Temple Church website.

Next Steps

Going forward, we plan to continue refining our processes and enhancing the functionality of the website. We'll aim to introduce more GitHub Actions workflows for other aspects of the development process, expand the documentation to cover new features and updates, and continue to optimize the code for efficient deployment and runtime performance.

We appreciate the support and contributions from all members of the development team and look forward to continued progress in future updates.