Releases: 2DSharp/FnCore
0.3.3 - Critical Patch
0.3.2 Patch
This is a patch release that improves v3.2.1:
- Fixes mongo indexing error due to version mismatch.
- Improves logging with full dates and full error + stack trace.
- Logs all throwables at main.
Release: 0.3.1
Improved release, good for the hackathon.
Change log:
- Improved logging
- Adds notification support with FCM, as a result, it requires a service account key file in
json
format from FCM admin console. - Fixes #8
- Internal API changes
- Added API methods for sending notifications and intelligently sending out notifications for similar requirements. Added Full-text search capabilities.
- Autoindexing through annotations.
Unstable 0.3.0-alpha1
Changelog
- New API changes, check proto file for updates.
- Added push notification via FCM support.
Still untested.
0.2.0 Stable
Release notes
The README file has been updated with build instructions.
CI/CD has been added for
- Docker with Cirrus CI
- Maven build with Github Actions
FnCore 0.2.0 comes with the following:
- New API changes. Check
src/main/proto
directory.- Fan out to users nearby.
- Cached feeds with redis.
- Better error handling and more descriptive naming.
- Configurable properties.
- Bug fixes.
- More tests for edge cases
- Improvement to maven build script
- Added docker builds
Release Candidate: 0.2.0-rc2
Release Notes
The availability of the release candidate marks one step closer to a full 0.2.0.
Changelog:
- Adds Configurable Properties
- More thoroughly tested and tiny bugs here and there
- Deprecated older repository methods (internal)
- Better error reporting
Unstable: 0.2.0-rc2.alpha.1 [configurable properties]
Release notes
This is an urgent test release to bring in configurable properties originally planned for 0.3.0.
This release allows consumers to start the server with a properties file which overrides the default configurable properties in the server.
The overriding rules are as follows:
-
The server will first look for an
fnconfig.properties
file in the same directory the server is being run from. If it finds one, it will try to load it and run with it. -
A
.properties
file can be passed as an argument to the server executable and it will try to load from those properties. -
If none of the above exist, the server will load from its default properties. This may work in some development systems, but most probably won't in production and isn't recommended.
Getting configurable properties allows the server to be decoupled from configuration and can be directly run without having to edit the supplied defaults in source and build.
Keeping the properties file safe is the responsibility of the one running the server. It may contain database secrets etc., which need to be protected. Do not put your fnconfig.properties
file in VCS.
An example properties file has been added in the root directory called fnconfig.examples.properties
. Rename it to fnconfig.properties
, edit the properties to your needs and run java -jar fncore-0.2.0-rc2.alpha.1.jar
.
You can also specify relative paths to property files without having to worry about the filename.
Release Candidate: 0.2.0-rc1
The first release candidate is ready and available!
Changelog:
-
New methods have been added, check the
src/main/fn_core.proto
file for details.- Deleting posts
- Getting user location details
-
BREAKING CHANGE: A slight refactoring has renamed the
RequestResult
response message toResponse
for ease of understanding. -
Solves platform-dependent builds #1
-
Added tests, almost stable for production.
-
Maven package profiles have been added to create better build names #5
-
External library logging has been disabled for the console.
Patch: 0.2.0-rc-alpha.3
This is a immediate patch release for 0.2.0-rc-alpha2
Changelog:
- Fixes issue #3, sends back distance
The next release will be RC2 for 0.2.0 with finalized tests.
Patch: 0.2.0-rc-alpha.2
This is a patch release for 0.2.0-rc-alpha
-
Fixes implementation binding for PostRepository at Guice Module.
-
More tests have been added, and implementations have been patched.
-
Redis caching is being read from configurations.
The API remains the same.