chore: Release v1.1.0

[nfebe]

[1.1.0] - 2026-06-13

Added

• Invitation accept and decline API endpoints, so an invited user can join (or turn down) a workspace through the same path that issues the invite
• MemberInvited and MemberJoined events are now dispatched (on invite and on accept), letting host apps react -- for example to send an invitation email

[sourceant]

Code Review Summary

This PR updates the workspace management package to version 1.1.0. It introduces essential features for handling workspace invitations (accept/decline) and implements an event-driven system to allow host applications to respond to membership changes.

🚀 Key Improvements

• Added API endpoints for accepting and declining invitations.
• Dispatched MemberInvited and MemberJoined events.
• Significantly expanded README documentation for API endpoints and events.
• Comprehensive test coverage for the new invitation flows.

💡 Minor Suggestions

• Consider case-insensitive email comparison.
• Refactor shared invitation validation logic in WorkspaceController.

[sourceant]

Review complete. See the overview comment for a summary.

[sourceant]

Using firstOrFail() with a non-ID lookup in an API context is generally fine, but consider whether you want to expose a 404 for an invalid token or a more specific 422 if the token simply doesn't exist. For tokens, 404 is appropriate, but ensure you have a custom exception handler if you want to return a JSON error message instead of the default HTML 404 page.

Suggested change

	$invitation = WorkspaceInvitation::where('token', $token)->firstOrFail();
	$invitation = WorkspaceInvitation::where('token', $token)->first();
	if (! $invitation) {
	return response()->json(['error' => 'Invalid or expired invitation token'], 404);
	}