Skip to content

Commit

Permalink
release: v1.1.16 (#171)
Browse files Browse the repository at this point in the history
🤖 I have created a release *beep* *boop*
---


##
[1.1.16](v1.1.15...v1.1.16)
(2024-11-27)


### Dependencies

* lock file maintenance
([#170](#170))
([c52db83](c52db83))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: eoeo-release[bot] <158570209+eoeo-release[bot]@users.noreply.github.com>
  • Loading branch information
eoeo-release[bot] authored Nov 27, 2024
1 parent edaefaa commit 603fee3
Show file tree
Hide file tree
Showing 4 changed files with 10 additions and 3 deletions.
2 changes: 1 addition & 1 deletion .release-please/.release-please-manifest.json
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
{
".": "1.1.15"
".": "1.1.16"
}
7 changes: 7 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,12 @@
# Changelog

## [1.1.16](https://github.com/eoeo-org/pow-summon-discordbot/compare/v1.1.15...v1.1.16) (2024-11-27)


### Dependencies

* lock file maintenance ([#170](https://github.com/eoeo-org/pow-summon-discordbot/issues/170)) ([c52db83](https://github.com/eoeo-org/pow-summon-discordbot/commit/c52db83a80a0291fe217e53e6931a0e41816e18a))

## [1.1.15](https://github.com/eoeo-org/pow-summon-discordbot/compare/v1.1.14...v1.1.15) (2024-11-20)


Expand Down
2 changes: 1 addition & 1 deletion Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion Cargo.toml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "pow-summon-discordbot"
version = "1.1.15"
version = "1.1.16"
edition = "2021"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
Expand Down

0 comments on commit 603fee3

Please sign in to comment.