Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

feat: add changelog to marketing #1190

Merged
merged 2 commits into from
Jun 20, 2024
Merged

feat: add changelog to marketing #1190

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a727abd
feat: add changelog to marketign
ElTimuro Jun 19, 2024
a2a10b0
chore: typo and format
ElTimuro Jun 20, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
45 changes: 45 additions & 0 deletions apps/marketing/content/changelog.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
---
title: Changelog - Documenso
description: Thoughts and details on the latest Documenso releases.
---

# Changelog
Check out what's new in the latest major version and read what we think about it. You can find our releases on GitHub for more technical details [here](https://github.com/documenso/documenso/releases). You can find our [release candidates here](https://github.com/documenso/documenso/tags).

---
## v1.5.5 (latest)
### <small>Released 6th May 2024</small>

> This release contains [20 fixes](https://github.com/documenso/documenso/releases/tag/v1.5.5)

### ✅ Show Completed Fields
Fields completed by other recipients are now visible to everyone to communicate the state of the document better and allow users an informed decision on what they are signing.

### ⬇️ Download Completed Documents via API
Completed documents can now be downloaded via the API using this new endpoint:

**GET /API/V1//DOCUMENTS/\{ID\}/DOWNLOAD**
Copy link
Contributor

Choose a reason for hiding this comment

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

Tip

Codebase Verification

The API endpoint syntax in the changelog file contains an extra slash after V1. The correct syntax should be /API/V1/DOCUMENTS/{ID}/DOWNLOAD.

  • Current incorrect endpoint: /API/V1//DOCUMENTS/{ID}/DOWNLOAD
  • Corrected endpoint: /API/V1/DOCUMENTS/{ID}/DOWNLOAD

Please update the endpoint accordingly.

Analysis chain

Verify the correctness of the API endpoint syntax.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify syntax correctness of the API endpoint.

# Test: Check if the API endpoint follows the correct syntax conventions.
echo "/API/V1//DOCUMENTS/{ID}/DOWNLOAD" | grep -P "^/API/V\d+/DOCUMENTS/\{ID\}/DOWNLOAD$"

Length of output: 91

Script:

#!/bin/bash
# Description: Verify syntax correctness of the API endpoint after removing the extra slash.

# Test: Check if the corrected API endpoint follows the correct syntax conventions.
echo "/API/V1/DOCUMENTS/{ID}/DOWNLOAD" | grep -P "^/API/V\d+/DOCUMENTS/\{ID\}/DOWNLOAD$"

Length of output: 122


Check out the full Open API docs here: [https://documen.so/openapi](https://documen.so/openapi)

### ➕ Adding Yourself as a Signer
Adding yourself as a signer is now just one click away.

---
## v1.5.4
### <small>Released 11th April 2024</small>

> This release contains [21 fixes](https://github.com/documenso/documenso/releases/tag/v1.5.4)

#### 🔑 Passkeys
To improve security and usability for high-security setups, we added passkeys with this release. Passkeys can now be used to log in or re-authenticate each signature for high-compliance cases.

#### 📄 Signing Certificate & Audit Log
On the security/ compliance side, we also added Signing Certificates and Audit Logs. Every signed document now has a certificate attached, showing technical details of the signature to improve transparency and security. Further, every action on a document from creation to completion is now logged in the audit log to guarantee the integrity of the process.

#### 🔏🦀 @documenso/pdf-sign
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can we add a GitHub repo link to this? @documenso/pdf-sign

We are pretty hyped about this one: Since version 0.9, we relied on https://github.com/vbuch/node-signpdf to add the digital signatures to our documents. Since signing is at the heart of Documenso, we created our own rust-based library for signing. As of 1.5.4, Documenso's signing runs on @documenso/pdf-sign. The library offers a better architecture to enable signing with private keys that are not stored locally (e.g. via HSM). We are in the process of cleaning up the library to open source it like the rest of Documenso 🌱 The library will also help us to offer Long Term Validation (LTV) for signatures soon. While we are currently limited to signing with PKCS7-B, eventually, we plan to support all common signing standards like PAdES, CAdES, and XAdES.
Copy link
Contributor

Choose a reason for hiding this comment

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

Consider using a hyphen for "Long Term Validation" to form "Long-Term Validation."

- Long Term Validation
+ Long-Term Validation
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
We are pretty hyped about this one: Since version 0.9, we relied on https://github.com/vbuch/node-signpdf to add the digital signatures to our documents. Since signing is at the heart of Documenso, we created our own rust-based library for signing. As of 1.5.4, Documenso's signing runs on @documenso/pdf-sign. The library offers a better architecture to enable signing with private keys that are not stored locally (e.g. via HSM). We are in the process of cleaning up the library to open source it like the rest of Documenso 🌱 The library will also help us to offer Long Term Validation (LTV) for signatures soon. While we are currently limited to signing with PKCS7-B, eventually, we plan to support all common signing standards like PAdES, CAdES, and XAdES.
We are pretty hyped about this one: Since version 0.9, we relied on https://github.com/vbuch/node-signpdf to add the digital signatures to our documents. Since signing is at the heart of Documenso, we created our own rust-based library for signing. As of 1.5.4, Documenso's signing runs on @documenso/pdf-sign. The library offers a better architecture to enable signing with private keys that are not stored locally (e.g. via HSM). We are in the process of cleaning up the library to open source it like the rest of Documenso 🌱 The library will also help us to offer Long-Term Validation (LTV) for signatures soon. While we are currently limited to signing with PKCS7-B, eventually, we plan to support all common signing standards like PAdES, CAdES, and XAdES.
Tools
LanguageTool

[uncategorized] ~44-~44: If this is a compound adjective that modifies the following noun, use a hyphen. (EN_COMPOUND_ADJECTIVE_INTERNAL)
Context: ... The library will also help us to offer Long Term Validation (LTV) for signatures soon. W...


---

´
1 change: 1 addition & 0 deletions apps/marketing/src/components/(marketing)/footer.tsx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,7 @@ const FOOTER_LINKS = [
{ href: '/oss-friends', text: 'OSS Friends' },
{ href: '/careers', text: 'Careers' },
{ href: '/privacy', text: 'Privacy' },
{ href: '/changelog', text: 'Changelog' },
];

export const Footer = ({ className, ...props }: FooterProps) => {
Expand Down
Loading