Repository navigation
Releases
v1.1.4-test.3
Testing code again
We be doing some testing here...
// Test code
const test1 = 2024;
const test2 = "Year";
console.log(`${test2}: ${test1}`);In this code example we set test1 to the current year, 2024.
We then console.log() it with the string "Year" and a colon infront.
v1.1.4-test.2 Test Release 3
// This is a test.
const test = "hello (:"
console.log(test)v1.1.4-test - Test Release 2
Header H1 - underlined
Header H2 - underlined
Header H3
Header H4
Header H5
Bold text
Italic text
Quote text
Code text
- Numbered List A
- Numbered List B
- Numbered List C
-
Unordered List A
-
Unordered List B
-
Unordered List C
-
Task List A
-
Task List B
-
Task List C
That seems to be all GitLab has to offer, at least as buttons.
v1.1.4 - Custom logger
1. Custom Logger Integration
A custom logger has been added to enhance the bot’s logging capabilities.
This logger provides structured and consistent log output, making it easier to debug and monitor the bot’s behavior.
Key benefits of the custom logger:
- Improved log readability with structured formatting.
- Supports multiple log levels to suit different debugging needs.
- Integrates seamlessly with existing configuration files and environment variables.
2. New Configurable Log Level Variable: logLevel
The logLevel variable has been introduced to give users fine-grained control over the verbosity of the bot’s logging.
Default Behavior:
The bot logs errors and warnings by default, ensuring critical issues are always highlighted without excessive log output.
Customizing Log Levels:
Users can enable more detailed logs (e.g., debug logs) by setting the logLevel via environment variables or configuration files.
This allows dynamic control over logging without altering the source code.
How to Use:
The bot only logs errors and warnings by default.
To enable debug logging, either set the environment variable DISCORD_BOT_LOG_LEVEL or app.debug.logLevel in config/development.yaml to DEBUG.
Authors: @Wurstkatze, @chatgpt
edit: why does the user chatgpt not exist but have a random profile picuture :/
v1.1.3 - API changes
We’ve made some important updates to the API in this release, which includes changes to several existing endpoints. These changes may affect how you interact with our API, so please review the following information carefully:
API Endpoint Changes:
- POST
/supporter_role/${guildId}-->/supporter_role: The guildId is given in the body of the post request now. [ecdb15a] - POST
/supporter_role: Variable name in body changed:guildId-->serverId[2e38a06]
These changes are part of our ongoing efforts to enhance the overall functionality and performance of our API. We recommend updating your integration to align with these adjustments to avoid potential issues in future versions.
If your application relies on any of the modified endpoints, please ensure that you update your implementation as needed. Failure to update may result in broken functionality or unexpected behavior.
For more detailed information on the changes and how to migrate your existing API calls, please refer to the updated API documentation.
Application Changes:
- Bot ready message changed:
Discord bot is ready!-->Discord bot is ready.
As always, thank you for using our service. If you encounter any issues or have any questions, feel free to reach out to our support team. Also, I love AI.
Full Changelog: v1.1.2...v1.1.3
v1.1.2
Now with a retry function whenever the backend is not available (at least on startup - if it's gone afterwards... well).
v1.1.1
v1.1.0
The bot is done!
Now with a Docker image in the GitHub Container Registry.
It includes a redis server. Might not be recommendet. I don't care.
Just has to work for the presentation.
Test Release
v0.1.0-a
First Pre-Release
Just a test of the release functionality.
- Bot features are done (mostly... probably)
- API doesn't work yet