Skip to content

Commit 1e8b46c

Browse files
tuhin18003tuhin18003
committed
security patch updated
1 parent c592bc2 commit 1e8b46c

File tree

2 files changed

+189
-0
lines changed

2 files changed

+189
-0
lines changed

‎CHANGELOG.md‎

Lines changed: 78 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,78 @@
1+
### Version: 1.1.9 ( June 02, 2025 ) ###
2+
- **Update:** Security patch updated
3+
4+
### Version: 1.1.8 ( January 07, 2025 ) ###
5+
- **Update:** Updated to WordPress & WooCommerce latest compatibility
6+
7+
### Version: 1.1.7 ( April 13, 2024 ) ###
8+
- **Update:** Updated to WordPress & WooCommerce latest compatibility
9+
10+
### Version: 1.1.6 ( January 09, 2024 ) ###
11+
- **Update:** Updated to WordPress & WooCommerce latest compatibility
12+
13+
### Version: 1.1.5 ( September 09, 2023 ) ###
14+
- **Update:** WordPress >= 6.3 & WooCommerce >= 8.0 version compatible
15+
16+
### Version: 1.1.4 ( April 06, 2023 ) ###
17+
- **Improvement:** WordPress 6.2 & WooCommerce > 7.5 compatible
18+
19+
### Version: 1.1.3 ( September 07, 2022 ) ###
20+
- **Fix:** Small bug fixed - page loading
21+
- **Improvement:** Upgrade on APP connecting time
22+
23+
### Version: 1.1.2 ( September 07, 2022 ) ###
24+
- **Fix:** Duplicate device registration fixed
25+
- **Fix:** Empty configuration bug fixed
26+
27+
### Version: 1.1.1 ( August 30, 2022 ) ###
28+
- **New:** Contact Form 7 - Receive push notification when someone submits the form
29+
- **Fix:** Major bug fixed - page loading
30+
31+
### Version: 1.1.0 ( August 19, 2022 ) ###
32+
- **New:** Receive push notification on - friend request cancelled
33+
- **New:** Receive push notification on - new activity published
34+
- **New:** Receive push notification on - new custom activity post type published
35+
- **New:** Receive push notification on - new custom activity post type updated
36+
- **New:** Receive push notification on - new custom activity post type deleted
37+
- **New:** Receive push notification on - new comment on post / activity status
38+
- **New:** Receive push notification on - new message received
39+
- **New:** Receive push notification on - new group invitation received
40+
- **New:** Receive push notification on - group details updated
41+
42+
### Version: 1.0.9 ( August 08, 2022 ) ###
43+
- **New:** Any users can receive push notifications
44+
- **New:** New settings panel on BuddyPress front-end (BuddyPress users can set to receive notifications)
45+
- **New:** Any users have access to the backend section to set up notifications for themselves
46+
- **New:** Full new interface for notifications settings section
47+
- **Fix:** BuddyPress notification minor bug fixed
48+
49+
### Version: 1.0.8 ###
50+
- **Improvement:** BuddyPress notification feature updated
51+
52+
### Version: 1.0.7 ###
53+
- **New:** BuddyPress notifications added (new friend request, friend request accepted, friend request rejected)
54+
- **Update:** SweetAlert2 updated to latest version
55+
- **Improvement:** WordPress 6.0 & PHP 8 compatible
56+
57+
### Version: 1.0.6 ###
58+
- **Improvement:** WordPress 5.9 compatible
59+
60+
### Version: 1.0.5 ###
61+
- **Improvement:** WordPress 5.8 compatible
62+
63+
### Version: 1.0.4 ###
64+
- **Improvement:** Improvement of configuration
65+
- **Update:** MeasurementID field is now optional
66+
67+
### Version: 1.0.3 ###
68+
- **Adjustment:** Updated to latest WordPress release
69+
70+
### Version: 1.0.2 ###
71+
- **Improvement:** Improvement of configuration
72+
- **Adjustment:** Updated to latest WordPress release
73+
74+
### Version: 1.0.1 ###
75+
- **Improvement:** Improvement of configuration
76+
77+
### Version: 1.0.0 ###
78+
- Initial release.

‎CONTRIBUTING.md‎

Lines changed: 111 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,111 @@
1+
# Ultimate Push Notifications Development Guidelines
2+
3+
* [Commit Message Standards](#commit-message-standards)
4+
5+
---
6+
7+
## <a name="commit-message-standards"></a> Git Commit Standards
8+
9+
To maintain a clean and understandable project history, we follow strict rules for writing git commit messages. These messages not only enhance readability but are also used to automatically generate the **Ultimate Push Notifications changelog**.
10+
11+
---
12+
13+
### Commit Message Structure
14+
15+
Each commit message should follow this structure:
16+
17+
```
18+
<type>(<scope>): <subject>
19+
20+
<body>
21+
22+
<footer>
23+
```
24+
25+
- The **header** is **mandatory**.
26+
- The **scope** in the header is **optional**.
27+
- Each line should be no longer than **100 characters**, to ensure readability on GitHub and other tools.
28+
29+
---
30+
31+
### Reverting a Commit
32+
33+
To revert a commit:
34+
35+
- Start the message with `revert:` followed by the original commit's header.
36+
- The body should include:
37+
`This reverts commit <hash>.`
38+
39+
> You can use the [`git revert`](https://git-scm.com/docs/git-revert) command to generate this automatically.
40+
41+
---
42+
43+
### Commit Types
44+
45+
Use one of the following types to describe the purpose of the commit:
46+
47+
- **New**: Introduce a new feature
48+
- **fix**: Resolve a bug
49+
- **Update**: Update code base
50+
- **docs**: Documentation-only changes
51+
- **style**: Code style changes (e.g., whitespace, formatting, semicolons)
52+
- **refactor**: Code changes that neither fix a bug nor add a feature
53+
- **perf**: Code changes that improve performance
54+
- **test**: Add or update tests
55+
- **chore**: Changes to tooling, build process, or non-code files
56+
- **ci**: CI/CD configuration changes (e.g., GitHub Actions, Travis)
57+
- **build**: Changes to build system or external dependencies (e.g., npm, webpack)
58+
59+
---
60+
61+
### Scope
62+
63+
Use a scope to clarify the area affected, for example:
64+
65+
- `Shipping`
66+
- `Tax`
67+
- `Vendor`
68+
69+
Use `*` if the change impacts multiple areas.
70+
71+
---
72+
73+
### Subject
74+
75+
The subject line should:
76+
77+
- Be written in **imperative, present tense** (e.g., “add”, “fix”, “update”)
78+
- Start with a **lowercase** letter
79+
- **Not** end with a period
80+
81+
Example:
82+
```
83+
fix(tax): correct calculation on inclusive tax
84+
```
85+
86+
---
87+
88+
### Body
89+
90+
In the body, use the imperative present tense.
91+
Describe:
92+
93+
- What was changed
94+
- Why the change was needed
95+
- How it differs from previous behavior
96+
97+
---
98+
99+
### Footer
100+
101+
Use the footer to:
102+
103+
- Highlight **breaking changes**
104+
Start with `BREAKING CHANGE:` followed by an explanation
105+
106+
- Reference GitHub issues using [closing keywords](https://help.github.com/articles/closing-issues-using-keywords/):
107+
`Closes #123`
108+
109+
---
110+
111+
For a more detailed explanation, refer to the full [Commit Message Style Guide](https://docs.google.com/document/d/1QrDFcIiPjSLDn3EL15IJygNPiHORgU1_OOAqWjiDU5Y/edit#).

0 commit comments

Comments
 (0)