# GA/OS v2.91.0 adds a people directory that groups multiple email addresses under one recruiter

The author of the portfolio platform GA/OS says release v2.91.0 adds a back-office people directory in which one recruiter can be linked to several addresses, shipped via pull request #223.

Canonical URL: https://freelancenews.online/news/ga-os-v2-91-0-adds-a-people-directory-that-groups-multiple-email-002f4760
Published: 2026-11-22T09:18:21.476Z
Updated: 2026-11-22T09:18:21.476Z
Source published: 2026-11-20T17:00:35.000Z
Event date: Not established
Review status: source-reviewed
Review method: Automated comparison against retrieved source text; not independent fact-checking.

## Report

The developer behind GA/OS, described in the post as a portfolio platform, has published a devlog covering release v2.91.0, which the author says adds a people directory to the product's back office. The author summarizes the change with a commit title quoted in the post: one recruiter, several addresses. The same account states the work shipped through pull request #223.

The stated motivation is specific to how the existing system keyed contacts. According to the author, recruiters often write from more than one mail address, and because contacts were keyed by sender address, the same person was split into separate records. The devlog presents the new directory as the response to that splitting.

Grouping is the mechanism the author describes. The post says that when a directory groups addresses under one person, differing sender addresses alone no longer force contacts to be handled as separate people. The release is built around a concrete capability, the author also states: several addresses can be linked to one recruiter.

The post is organized around two things: the new people directory in the back office, and how addresses are consolidated under a single person. It also points readers to the v2.91.0 release on GitHub and carries a line stating the piece was first published on giannialagna.me.

For freelancers, designers and developers who maintain their own back-office tooling, the change is a small but concrete example of a modeling decision. Keying a contact record on a single email address assumes one address per person; the author's account shows a case where that assumption produced duplicate records and where the fix was to let one person hold several addresses. That is editorial interpretation of the author's stated rationale, not a measured result.

The evidence does not go beyond that rationale. The devlog does not describe the data model behind the directory, how addresses are matched to a person, whether grouping is done manually or automatically, or what happens to records that were already split before the release. It also does not say whether a grouping can be undone if two different people are combined by mistake.

Nor does the post report any testing, scale or outcome. There is no count of contacts, no before-and-after measure of duplicate records, and no comparison with alternative approaches. The author does not claim a reduction in duplicates; the benefit described is the intended behavior of the new directory, not a demonstrated one.

Availability is likewise undocumented in the supplied text. The post does not state pricing, whether the platform is open to users beyond the author, or whether the directory is exposed anywhere outside the back office. The GitHub release and pull request are referenced as links, but their contents are not included in the evidence, so the code-level specifics remain unverified here.

What the post does establish is traceability. The author ties the change to a version number, v2.91.0, and to a specific pull request, #223, and the write-up carries a first-publication line pointing to the author's personal site. For readers who follow small projects, that pairing of version and pull request is the kind of detail that makes a changelog entry checkable, even though the linked artifacts themselves are outside the supplied material.

A second point worth separating from the release itself is the framing. The author presents this as a back-office addition to a personal portfolio platform, not as a general-purpose product announcement. The post is a devlog about one change, and the claims in it should be read as the author's account of their own work rather than as independently verified facts.

For this audience, the practical implication is a design prompt rather than a reference implementation. If you keep a contact list for client or recruiting correspondence in a custom tool, deciding whether a person or an address is the primary record is a real choice, and the author's approach of attaching several addresses to one person is one way to make it. Whether it fits your tooling depends on details the post leaves out.

Those gaps matter if you were considering copying the pattern. Matching logic, migration of existing duplicates, the ability to split an incorrect grouping, and any limit on addresses per person are all unaddressed in the supplied text. Without them, the post describes an outcome and a rationale but not a method another developer could follow.

The conclusion is correspondingly modest. Per the author's devlog, GA/OS v2.91.0 adds a people directory to the back office, lets one recruiter be linked to several addresses, and shipped via pull request #223. It is a concrete, attributable change to a personal project; its value to other developers lies in the modeling idea the author describes, not in any documented outcome.

## Key points

- The author states that GA/OS release v2.91.0 adds a people directory to the platform's back office.
- According to the post, the directory groups several email addresses under one person so contacts are not split by sender address.
- The author says one recruiter can be linked to several addresses, and that the change shipped via pull request #223.
- The devlog does not describe matching logic, migration of existing duplicate records, testing, metrics, pricing or availability.

## Practical implications — editorial interpretation

Editorial interpretation: the release is a prompt to check how your own contact tooling keys records — if a single email address is the primary key, one person with several addresses becomes several contacts. The author's approach of linking multiple addresses to one person is one way to handle that, but the source gives no implementation detail, so treat it as a design question rather than a reference implementation.

## Limitations and unknowns

The only evidence is the author's own devlog on dev.to, which carries a line stating it was first published on giannialagna.me; the referenced GitHub release and pull request #223 are not supplied, so the change is unverified. The post omits matching logic, handling of existing duplicate records, ability to split an incorrect grouping, address limits per person, testing and metrics. No pricing, availability or user base is described.

## Sources

- [1] dev.to: v2.91.0: People directory with several addresses per recruiter
  https://dev.to/giannialagna-me/v2910-people-directory-with-several-addresses-per-recruiter-4f9m
  Retrieved: 2026-11-22T09:17:35.788Z

## Claim references

- GA/OS v2.91.0 adds a people directory to the platform's back office, per the author. [source 1]
- The author says contacts keyed by sender address split the same person into separate records. [source 1]
- The author states that grouping addresses under one person means contacts are not treated as separate people just because the sender address differs. [source 1]
- The author says one recruiter can be linked to several addresses. [source 1]
- The author states the change shipped via pull request #223. [source 1]
