fix: client posts generating improvements #24
Merged
Conversation
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
…in-client-posts-generating-improvements
KacperKoza343
force-pushed
the
feat/linkedin-client-posts-generating-improvements
branch
from
5f1bf38 to
a1a62c5
Compare
KacperKoza343
changed the title
| @@ -1 +1 @@ | |||
| {"version": "0.1.8+build.1"} | |||
| {"version": "0.1.9-alpha.1"} | |||
There was a problem hiding this comment.
it should be part of this PR?
There was a problem hiding this comment.
This change was auto generated, but the same version is currently in target repo: https://github.com/elizaOS/eliza/blob/develop/client/src/lib/info.json so I think we can leave it here
mgacek-blockydevs
approved these changes
Jan 22, 2025
KacperKoza343
merged commit e9cb03f
into
feat/linkedin-client-posts-automation
4 of 5 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Relates to
Risks
Background
What does this PR do?
What kind of change is this?
Documentation changes needed?
Testing
Where should a reviewer start?
Detailed testing steps