chore(main): release 1.7.1

[github-actions]

🤖 I have created a release beep boop

1.7.1 (2024-08-24)

Bug Fixes

• error when closing the result buffer and trying to reopen it (#188) (ddce6f8)
• split: remove redundant buffer name setting (88dd2ff)

---

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

• Bug Fixes
  • Resolved an issue that caused errors when closing and reopening the result buffer, improving stability.
  • Removed redundant buffer name setting in the split functionality for a more streamlined user experience.
• Chores
  • Updated the version number to 1.7.1 to reflect the recent bug fixes and enhancements.

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7c95428

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

The application has been updated to version 1.7.1, released on August 24, 2024. This version includes two key bug fixes: one resolves an error related to reopening the result buffer, while the other removes redundant buffer name settings in the split functionality. These updates aim to improve the application's stability and usability.

Changes

Files	Change Summary
CHANGELOG.md	Added version entry for 1.7.1, detailing two bug fixes.
version.txt	Updated version from 1.7.0 to 1.7.1.

Poem

In the burrow, changes spry,
Bugs are fixed, oh me, oh my!
Buffers close, then open wide,
Hopping forth with joyful pride!
A version bump, our tails do wag,
A happy code, no reason to lag! 🐇✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 88dd2ff and 7c95428.

Files selected for processing (2)

• CHANGELOG.md (1 hunks)
• version.txt (1 hunks)

Files skipped from review due to trivial changes (1)

• version.txt

Additional comments not posted (1)

CHANGELOG.md (1)

3-8: LGTM! The new version entry is well-structured.

The new version entry for 1.7.1 is correctly formatted and includes relevant links to issues and commits.

[github-actions]

🤖 Release is at https://github.com/jellydn/hurl.nvim/releases/tag/v1.7.1 🌻