-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #119 from truthencode/synk-for-swm
update minor bumps
- Loading branch information
Showing
2 changed files
with
58 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
--- | ||
title: Bump pegdown from 1.5.0 to 1.6.0 | ||
--- | ||
# Introduction | ||
|
||
This document will walk you through the implementation of the version upgrade feature for the `pegdown` library in our project. The `pegdown` library is a pure-Java Markdown processor that we use for parsing and converting Markdown into HTML in our application. We will cover: | ||
|
||
1. Why we decided to upgrade the `pegdown` library version. | ||
|
||
2. How the version upgrade was implemented. | ||
|
||
# Why upgrade the pegdown library version? | ||
|
||
The `pegdown` library is a crucial part of our application as it handles the conversion of Markdown to HTML. Keeping this library up-to-date is important for several reasons: | ||
|
||
- **Security**: Newer versions often include patches for security vulnerabilities that have been discovered since the last release. | ||
|
||
- **Performance**: Updates often come with performance improvements, making our application faster and more efficient. | ||
|
||
- **New Features**: Upgrading to the latest version allows us to take advantage of any new features or improvements that have been added. In this case, we decided to upgrade from version 1.5.0 to 1.6.0 to benefit from the improvements and fixes introduced in this new version. | ||
|
||
# How was the version upgrade implemented? | ||
|
||
<SwmSnippet path="/pom.xml" line="979"> | ||
|
||
--- | ||
|
||
The version upgrade was implemented by modifying the file, which is the Project Object Model file for our Maven project. This file contains information about the project and configuration details used by Maven to build the project. In the file, we updated the version of the `pegdown` library from 1.5.0 to 1.6.0. This tells Maven to use version 1.6.0 of the `pegdown` library when building our project. | ||
|
||
```xml | ||
<version>1.6.0</version> | ||
``` | ||
|
||
--- | ||
|
||
</SwmSnippet> | ||
|
||
By making this change, we ensure that our application is using the latest, most secure, and efficient version of the `pegdown` library. This will help to improve the overall performance and security of our application. | ||
|
||
<SwmMeta version="3.0.0" repo-id="Z2l0aHViJTNBJTNBZGRvLWNhbGMlM0ElM0F0cnV0aGVuY29kZQ=="><sup>Powered by [Swimm](https://app.swimm.io/)</sup></SwmMeta> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
--- | ||
title: Effects | ||
--- | ||
```mermaid | ||
gantt | ||
title A Gantt Diagram | ||
dateFormat YYYY-MM-DD | ||
section Section | ||
A task :a1, 2014-01-01, 30d | ||
Another task :after a1 , 20d | ||
section Another | ||
Task in sec :2014-01-12 , 12d | ||
another task : 24d | ||
``` | ||
|
||
<SwmMeta version="3.0.0" repo-id="Z2l0aHViJTNBJTNBZGRvLWNhbGMlM0ElM0F0cnV0aGVuY29kZQ=="><sup>Powered by [Swimm](https://app.swimm.io/)</sup></SwmMeta> |